-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Sandbox: crash when sending non-cloneable elements back via contextbridge #157765
Comments
From the stack trace, the crash is caused by an JS exception being triggered when receiving some IPC message in preload and the exception does not get handled causing it to be propagated to workbench. Since we have enabled sandbox which also implies context isolation, the exception created in preload v8 context cannot be handled by workbench which lives in a different v8 context causing this abort from the runtime. I will need to investigate further on what exception is triggered and why we don't handle it in the preload script.
|
Ah yeah true, I forgot that this could also just be sandbox related and not Electron related... |
Confirmed it is related to sandbox and what might be related is that I always see this error: Suggesting that vscode/src/vs/base/parts/sandbox/electron-browser/preload.js Lines 94 to 104 in 337d420
|
I can confirm it is related to slow resolving shell env, so its probably reproducable even running out of sources. I had commented out this from my
|
resolveShellEnv
times out
It just reproduced without OS restart, so it is unrelated to that, it was just that OS restart made it happen easily. |
resolveShellEnv
times outipcMain
ipcMain
I am fine closing this given the mitigation. |
Closing as issue has been inactive for a while and not priority at the moment. |
I noticed that after a restart, I am greeted with the following dialog:
Managed to get a crash dmp:
b98c6b58-72f2-4348-9954-e7d58fc789be.dmp.zip
This does not reproduce with stable. I think this is quite bad and would block a E19 update.
Steps:
The text was updated successfully, but these errors were encountered: