Bug 176829 - crash on exit in ~KBookmarkMenu()
Summary: crash on exit in ~KBookmarkMenu()
Status: RESOLVED DUPLICATE of bug 173634
Alias: None
Product: amarok
Classification: Applications
Component: File Browser (show other bugs)
Version: 2.0-SVN
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-03 22:37 UTC by Alex Sidorenko
Modified: 2008-12-03 23:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Sidorenko 2008-12-03 22:37:38 UTC 
Version:           2.0-rc1 (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

To duplicate:

- start amarok
- go to 'Files' view, navigate to a directory, add it to bookmark
- start playing, then stop
- quit

Approximately 1 time out of 3 amarok crashes with the following stack:


Application: Amarok (amarok), signal SIGSEGV
(no debugging symbols found)
...
[KCrash handler]
#5  0x0000000002e40034 in ?? ()
#6  0x00007f8323d8320e in KBookmarkMenu::~KBookmarkMenu ()
   from /usr/lib/libkio.so.5
#7  0x00007f832710cac8 in ?? () from /usr/lib/libamaroklib.so.1
#8  0x00007f83260be601 in QObjectPrivate::deleteChildren ()
   from /usr/lib/libQtCore.so.4
#9  0x00007f83256258cd in QWidget::~QWidget () from /usr/lib/libQtGui.so.4
#10 0x00007f8327105884 in ?? () from /usr/lib/libamaroklib.so.1
#11 0x00007f832707e995 in MainWindow::deleteBrowsers ()
   from /usr/lib/libamaroklib.so.1
#12 0x00007f832706edab in App::~App () from /usr/lib/libamaroklib.so.1
#13 0x0000000000404032 in _start ()
#0  0x00007f832513e621 in nanosleep () from /lib/libc.so.6

Regards,
Alex
Comment 1 Casey Link 2008-12-03 22:43:01 UTC 
i can reproduce this bug.

in addition: the crash will happen on exit every time, until the bookmark is removed.

Also: Kate suffers from this bug too.

That's what we get for snaking code ;)
Comment 2 Seb Ruiz 2008-12-03 23:05:13 UTC 

*** This bug has been marked as a duplicate of bug 173634 ***