-
Notifications
You must be signed in to change notification settings - Fork 1
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
Attempting to create multiple WebViews crashes the program (on Mac OS only?) #77
Comments
A few
Not sure if that will help. Also need to test more on Windows/Linux, but that's left for later since OSX is the bigger problem. |
I guess for the time being webviews can be limited to one instance per app, even if it's not ideal. But the SEGFAULT needs to go. |
This needs to be fixed properly so that we can create multiple webviews and destroy them at will, without SEGFAULT on OSX. Right now we can't, and I don't particularly feel like digging through the arcane Objective C code in webview itself, so this will have to do. It's tracked via #77 so the info won't get lost.
This needs to be fixed properly so that we can create multiple webviews and destroy them at will, without SEGFAULT on OSX. Right now we can't, and I don't particularly feel like digging through the arcane Objective C code in webview itself, so this will have to do. It's tracked via #77 so the info won't get lost.
As shown by the SEGFAULT in #155, the problem is even more severe: There can't just be a single WebView that's currently active, but creating any view after the first seems to instantly crash the runtime. That makes it quite annoying to test, and it also means that no long-running program can create more than a single, global/shared view without crashing. Unfortunately, fixing this would mean replacing a lot of the OSX specific code in the webview library. Is there an easy way out? |
Waiting for #201 to be completed. |
This seems to be a limitation of the upstream library:
Crashes with SEGFAULT on Mac OS. Fails with GTK warning in WSL?
The text was updated successfully, but these errors were encountered: