You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
node::IsolateData allocates V8 objects before initializing platform #20171
The constructor of node::IsolateData allocates strings in V8 heap before registering itself with the platform. This is not safe because an allocation can trigger GC, which relies on the platform to post tasks.
The problem reproduces with --stress-incremental-marking flag.
I'm encountering the exact error above in a node script I'm running. I'm using node 10.13.0, which was released after this fix seems to have been committed. Was this change included in 10.13.0?
But if I run node --stress-incremental-marking as the OP reports, I just get the node prompt, no errors.
Other searches for the same error yielded only people finding bugs on ARM architectures, but I'm on a recent Macbook.
Looks like it was added to 10.1.0, if I'm reading this page correctly. So I guess there's more than one way to cause this problem. I realize this is not a support forum, but any tips would be welcome!
@nathancarter the assertion looks similar, but the root cause might be different.
Your stack trace suggests that node is already running some script (lines 18-21 looks like generated code). In my case the crash happened during node initialization before running the scripts.
I'd suggest opening a new issue with steps to reproduce.
Activity
addaleax commentedon Apr 20, 2018
I think that’s fine, yes.
src: create per-isolate strings after platform setup
src: create per-isolate strings after platform setup
src: create per-isolate strings after platform setup
src: create per-isolate strings after platform setup
nathancarter commentedon Jan 22, 2019
I'm encountering the exact error above in a node script I'm running. I'm using node 10.13.0, which was released after this fix seems to have been committed. Was this change included in 10.13.0?
But if I run
node --stress-incremental-markingas the OP reports, I just get the node prompt, no errors.Other searches for the same error yielded only people finding bugs on ARM architectures, but I'm on a recent Macbook.
Am I barking up the wrong tree here?
nathancarter commentedon Jan 22, 2019
Looks like it was added to 10.1.0, if I'm reading this page correctly. So I guess there's more than one way to cause this problem. I realize this is not a support forum, but any tips would be welcome!
ulan commentedon Jan 22, 2019
@nathancarter the assertion looks similar, but the root cause might be different.
Your stack trace suggests that node is already running some script (lines 18-21 looks like generated code). In my case the crash happened during node initialization before running the scripts.
I'd suggest opening a new issue with steps to reproduce.
nathancarter commentedon Jan 23, 2019
OK. I'll do that as soon as I can get to a minimal working example. Current example is huge. Thanks!