[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 265626] Amarok crash while browsing files [@ Amarok::ElidingButton::qt_metacall]
From:       Ian Monroe <ian.monroe () gmail ! com>
Date:       2012-10-26 20:16:35
Message-ID: bug-265626-17878-io5HGVIqvi () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=265626

--- Comment #32 from Ian Monroe <ian.monroe@gmail.com> ---
Created attachment 74818
  --> https://bugs.kde.org/attachment.cgi?id=74818&action=edit
patch to possibly fix a related crash

So I've been looking into the issue in the morning. I found a new crash that I
think is unrelated to the main issue; the patch for that is attached. I'm
hesitant to submit it because it doesn't actually fix the crash caused by
messing with the bread crumb widget.

This is what I think is happening:
The Amarok bread crumb widget uses QPushButton.setMenu. Unfortunately
QPushButton uses QMenu::exec, which is an synchronous function which commits
evil and dips into the eventloop (QPushButton uses it even though it doesn't
even use the QAction that it returns!). It gets all confused when it goes into
the event loop and then QMenu deletes itself somewhere along way and crashes. 

So we should think about filing a Qt bug, but it's possible I'm not reading the
qmenu.cpp code correctly. 

For Amarok the fix for the bug is probably to not use QPushButton.setMenu.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]