-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
matemenu-tree: Fix crash when adding launcher from compact menu #117
matemenu-tree: Fix crash when adding launcher from compact menu #117
Conversation
The emit_changed_signal callback was attempting to run on a submenu that had already been destroyed by its parent menu. Closes mate-desktop#116
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still got the same crash (under wayland, will check x11 too) with
corrupted size vs. prev_size while consolidating
Aborted
after applying this. EDIT: identical results under x11
I can confirm that using this PR drop the valgrind output from #116 (comment) when adding a launcher. |
We need to recheck why author and reviewers get different results. From my point of view PR looks good. |
@zhuyaliang |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was able to reproduce the crash and can confirm that PR fixes the crash for me in fedora.
@lukefromdc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still got the same
corrupted size vs. prev_size while consolidating
Aborted
while running under wayland
same crash in x11 too. Note that I am running locally compiled GTK 3.24.39 with the gtk3-classic patches applied and locally compiled glib 2.78.3 |
I am still wondering about the crash description. |
I see only this in terminal:
Also with valigrind i do not see your message. |
I saw it in terminal after running |
Weird, that we get different outputs in terminal. |
@cwendling |
@lukefromdc any chance we could get a GDB backtrace or Valgrind report when it happens? |
I got this from
|
I got this backtrace from gdb:
|
Can you check that the compiled mate-menus library is being used when you run
I'm wondering if there's an issue with |
libmate-menu.so.2 => /lib/x86_64-linux-gnu/libmate-menu.so.2 (0x00007f1e2add0000) Note that I have all of MATE locally compiled, my Checkinstall(for autotools) or DESTDIR (for meson) .deb files install to the exact same locations as my direct installs. |
@cwendling |
I didn't get any NEW problems with this, it just didn't fix an existing problem. If these are two different crashes, than not fixing one is no reason not to fix the other. I've had this installed from last build for a while with same behavior as master on my system. |
Thx. |
@lukefromdc |
It most certainly did, and continued to do so after I added the second commit to mate-desktop/mate-panel#1434 to return to GtkImageMenuItem (already referred to in the header file after the revert) for the Places and System main menu items |
The
emit_changed_signal
callback was attempting to run on a submenu that had already been destroyed by its parent menu.Closes #116
Testing
mate-panel --replace