-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v8 crash when loading wasm in extension host #115646
Comments
The difference between the chrome and node arise from the use of different page allocator for v8. Chrome renderer uses Gin's v8 page allocator which inturn depends on partition_alloc to handle I can push that as a fix for vscode but the root issue needs to be investigated in node as they can't do such a switch. |
\closedWith ff85144 |
Out of curiosity. How does the electron bump fix it? I wasn't able to find anything relevant in the commit history. |
The allocator switch has been made in our internal electron builds for early testing, we will create a PR in OSS electron with the same change sometime this week. |
Sorry to ask here, but I've been poking around, can't find a solid answer, and don't want to break vscode on my M1. Is the latest insiders build now working with macOS 11.2 in cases where this issue popped up? |
Yes! |
I'm seeing this error in the developer tools with the latest insiders. cc @deepak1556 Just noticed it's related to an extension. That same extension works on Stable though. Edit: False alarm: could be an extension problem. I actually see the same error logged on Stable, but everything seems to work both on Insiders and Stable. |
Can you open an new issue for that extension |
@andreialecu I think that is a problem with the bracket pair colorizer 2 extension (AFACIT it is using |
Was my initial suspicion as well. I can also confirm that latest insiders works great on MacOS |
I'm using VSCode with Salesforce. Any advice greatly appreciated! Log Info: |
Can you try the universal build or arm64 build insiders version https://code.visualstudio.com/insiders and see if the issue persists. |
Created from #113410 (comment)
Minimal electron repo: https://gist.github.com/deepak1556/a6d791b204978aeed549347b6c55d124
StackTrace: #113410 (comment)
Upstream issue in node: nodejs/node#37061
The issue is only with process running as node.
The text was updated successfully, but these errors were encountered: