-
Notifications
You must be signed in to change notification settings - Fork 1.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
tray: cairo_surface_reference assertion failure #11984
Comments
@Semphriss, can you take a look? |
@Green-Sky Can you send a minimal reproducible code sample and specify when and how consistently the crash happens? Since the crash happens in |
Yes, you'll definitely have to do that. |
By the way, we're planning a release candidate build in the next few days, so if you can get to your tray bugs soon that would be great. |
Got another.
Rare, sometimes minutes, sometimes days after the application is started. I don't really do much, the only thing that is set pretty often is the icon. Everything else is static (there are 2 buttons in the menu that are set once). edit: This one is slightly different, so I'm adding it here: Details
|
Is there some other activity (specifically, calling tray-related functions) happening while the crash happens, or is it just not doing anything and waiting? Also, do you use GTK3 elsewhere in your application? |
The only thing that happens is set icon.
No I don't use any GTK, besides the tray/whatever else SDL might be doing. Set icon is called when there is a new unread message, and called again when there is no longer. https://github.com/Green-Sky/tomato is the app. It might be possible to trigger this by spamming set icon, if that is the bug. |
GTK+ documentation states that all GDK and GTK+ calls should be made from the main thread. Fixes libsdl-org#11984
GTK+ documentation states that all GDK and GTK+ calls should be made from the main thread. Fixes libsdl-org#11984
GTK+ documentation states that all GDK and GTK+ calls should be made from the main thread. Fixes libsdl-org#11984
GTK+ documentation states that all GDK and GTK+ calls should be made from the main thread. Fixes libsdl-org#11984
GTK+ documentation states that all GDK and GTK+ calls should be made from the main thread. Fixes libsdl-org#11984
All tray operations happen on the main thread, so there should no longer be any race conditions in the tray code. Please let us know if you're still getting crashes in the latest main code. |
Having the tray exist can cause a random crash.
Linux (nixos) using
libayatana-appindicator
commit 355f69e
Same crash also previously reported in #11893
The text was updated successfully, but these errors were encountered: