-
Notifications
You must be signed in to change notification settings - Fork 178
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
Activating a view from cairo-dock crashes wayfire #772
Comments
What call is cairo-dock making in this case? |
zwlr_foreign_toplevel_handle_v1_activate() zwlr_foreign_toplevel_handle_v1_activate() But the crash does not happen instantly. Actually, it does not happen at all if I set a breakpoint at this line and single step or even if I just continue after the break. It still happens if I run it in a debugger without setting a breakpoint. |
This seems to be a race condition, and hitting this assert would usually mean a bug in wlroots. Have you tried running with ASAN to rule out that Wayfire corrupts the memory? |
Just tried it, ASAN does not report any errors related to this. I get the following error, but I think it is unrelated:
Telling it to ignore this, i only see memory leaks reported if terminated normally, but not anything if the crash is triggered. |
I looked into this a bit more:
|
Fixed in wlroots: swaywm/wlroots#2454 |
Steps to reproduce:
cairo-dock -o -L
)Expected result: app is restored and activated
Actual result: wayfire crashes (see below for stacktrace)
In this case, cairo-dock is using the activate request of wlr-foreign-toplevel-management.
The crash does not happen if left clicking on the application icon (app is restored and activated) and also does not happen with wf-dock -- both of these methods use the same interface. The crash happens on master without my changes to the foreign toplevel protocol.
Output from wayfire:
The text was updated successfully, but these errors were encountered: