-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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 backingstore crash in nwjs 0.45 #7519
Comments
Looking through the abort is likely the CHECK here: void GlobalBackingStoreRegistry::Register( if (!backing_store->free_on_destruct()) {
} |
Looks like this is a node 14 bug that was fixed in 14.3. If that the case this can be closed. see nodejs/node#33321 |
Please try the latest version. Thanks. |
@rogerwang We cant try 0.46 yes due the Chromium 83 cross-origin changes we haven't worked around yet but I did backport the nodejs bug fix to 14.2 and 0.47 and the crash is gone. |
@mkilburn60 you can file an issue about the the cross-origin changes. NW App shouldn't be restricted by it under the default security model. |
Hi,
We have a problem with nwjs crashing but its very hard to reproduce and the app is very complex. Previously we were using nwjs 0.20 and recently upgraded to 0.45.
Here is a backtrace from Windows. The same crash with the same backtrace happens on Mac. I'd like some help understanding this backtrack.
To me it looks like a problem with V8 backingstore. XMLHttpRequest from Chromium is going through nodes V8 and I'm wondering if the is a problem with using a common V8 for both node and Chromium in nwjs.
Any insights would be greatly appreciated.
@rogerwang
The text was updated successfully, but these errors were encountered: