Skip to content
This repository was archived by the owner on Oct 15, 2020. It is now read-only.

crash upon Number.MAX_VALUE.toString(16) #509

Closed
Tracked by #3087
alexlamsl opened this issue Mar 31, 2018 · 8 comments
Closed
Tracked by #3087

crash upon Number.MAX_VALUE.toString(16) #509

alexlamsl opened this issue Mar 31, 2018 · 8 comments

Comments

@alexlamsl
Copy link

  • Version: v8.10.0
  • Platform: Windows 10 x64

Node.js

$ node -v
v8.11.1

$ echo Number.MAX_VALUE.toString(16);console.log("Done") | node
Done

$

node-chakracore

$ node -v
v8.10.0

$ echo Number.MAX_VALUE.toString(16);console.log("Done") | node

$
@alexlamsl
Copy link
Author

Pure speculation - this may be a regression caused by the fix for #390 & chakra-core/ChakraCore#2751

@MSLaguana
Copy link
Contributor

I think that I fixed this in upstream chakracore a couple of days ago; not sure if the change has made it into a nightly build yet. Thanks for reporting it though!

@MSLaguana
Copy link
Contributor

Just confirmed; the fix is in the chakracore-master branch here, but nightlies are currently built from master which is tracking a previous branch in upstream chakracore. This will be changing in the near future I think, so it should be resolved at that time.

@alexlamsl
Copy link
Author

Thanks for the information (& the fix) – shall I close this since it's already fixed upstream?

@MSLaguana
Copy link
Contributor

I'm inclined to leave it open until the fix makes it into a build somewhere.

@alexlamsl
Copy link
Author

Still an issue as of v10.0.0

@alexlamsl
Copy link
Author

Still an issue as of v10.1.0

@alexlamsl
Copy link
Author

Fixed in v10.6.0 - thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants