-
-
Notifications
You must be signed in to change notification settings - Fork 403
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
Nyxt crashes when changing buffers repeatedly #3393
Comments
I can't reproduce it but I'll keep an eye on it. Try to run |
Running into the same issue with crashing (but not having the failure to create cache issue). Built from source.
|
@fictitiousexistence that seems to suggest that the issue may be related to a new WebKitGTK version. |
@aadcg Thank you. Gentoo updated from webkit 2.42.5 to 2.44.1 and dropped 2.42.5. I rebuilt 2.42.5 and confirmed it no longer happens. I couldn't get anything between those 2 versions to build so I'm not sure when it started. Is this completly different from original issue here and not a nyxt issue but strictly webkit-gtk and a bug should be filed over there? |
@fictitiousexistence the error reported here seems to be related to webkitgtk alone. Nyxt seems to be running fine on Flatpak, which is using webkitgtk 2.44.0. In order to report a bug to webkitgtk, we'd need to understand what exactly is going on, i.e. it may be related to https://github.com/joachifm/cl-webkit or webkitgtk itself. |
I'm experiencing a similar issue on OpenSUSE Tumbleweed. No matter if i use the .rpm or the .flatpak: switching buffers repeatedly (or even randomly) causes Nyxt to crash. I have no custom config installed. This is the output from the flatpak:
|
Are you using Wayland GNOME? I get crashes all over the place using Niri.
Trying to access internal documentation pages, and when restore history is enabled, or just random tab changes. These crashes go away when I run it in an X.org session or inside Xwayland. A quick search would indicate there is a bug with GTK3/Wayland interaction. I have tried different versions of webkitgtk, nyxt, cl-webkit2, flatpaks, etc. All have the same issue, but only when on Wayland. Update 1: LIBGL_ALWAYS_SOFTWARE=1 makes crashes go away too. I'm using this on a laptop with NVIDIA prime. If I force offloading DRI_PRIME=1, this also fixes the crashes for me. I can test how it behaves for me on an AMD GPU a bit later. Update 2: Crashes out with AMD GPU as well. Running with EGL_LOG_LEVEL=debug spits out a bunch of this error
Looks to be a threading issue.
Update 3: Disabling composting makes fixed it too. WEBKIT_DISABLE_COMPOSITING_MODE=1 |
@lugeha, indeed, it is documented in the manual to set that variable when the renderer misbehaves. Can someone reproduce any of the issues mentioned after setting the mentioned environment variable? |
@aadcg Upgraded webkit back to 2.44.1. |
@aadcg to be fair, it only really mentions blank pages, not hard crashes. |
Describe the bug
Switching buffers makes the browser eventually crash, this happens regardless of the amount of buffers open.
It's triggered more easily when switching rapidly, say to load the buffers that were open in a previous session.
No idea if this means it's loading something extra when switching and this corrupts memory in some way? The terminal output doesn't reflect that.
In the "Output from terminal" you will notice that it complains of not being able to create
/home/lmcj/.var/app/engineer.atlas.Nyxt/cache
, however when I look for it the directory exists and within it there are three directories, namelyfontconfig
,mesa_shader_cache
andtmp
.Also, it complains about it every time it's loading a buffer.
You will also see in the output from terminal that I loaded 3 buffers, this was a result of me changing buffers which were loaded from the history, once the buffers were loaded I continued changing buffers, naturally no more loading was done, but then suddenly the last part of the output is printed, which is when it crashed.
Precise recipe to reproduce the issue
For website-specific issues:
N/A
Information
show-system-information
:Output when started from a shell
The text was updated successfully, but these errors were encountered: