Summary: | Crash when removing (or adding) removable device [@ Handler::UmsReadCapability::setAssociateTrack] | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | David Solbach <d> |
Component: | Collections/USB mass storage and MSC | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | aumuell, bart.cerneels, bernardo, ivan, matej, mprizee, mr.explosion, ralf-engels, realzork, trumpetthor+bug, vvasaitis |
Priority: | HI | Keywords: | release_blocker |
Version: | 2.5.0 | ||
Target Milestone: | 2.6 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
Description
David Solbach
2010-07-05 23:33:45 UTC
Created attachment 48764 [details]
New crash information added by DrKonqi
amarok (2.3.1) on KDE Platform 4.4.90 (KDE 4.4.90 (KDE 4.5 RC1)) using Qt 4.7.0
- What I was doing when the application crashed:
I had just waited about one hour for amarok to finish scanning my external hd for my music collection. After the hd activity had stopped for about 10 minutes, and no file showed in amarok, I tried clicking the eject button.
- Unusual behavior I noticed:
Amarok crashed
- Custom settings of the application:
None, started with a clean configuration.
-- Backtrace (Reduced):
#8 0x00d8c690 in Meta::MediaDeviceHandler::privateParseTracks (this=0x4f0049) at ../../src/core-impl/collections/mediadevicecollection/handler/MediaDeviceHandler.cpp:840
#9 0x00d8de05 in Meta::ParseWorkerThread::run (this=0x9f72d90) at ../../src/core-impl/collections/mediadevicecollection/handler/MediaDeviceHandler.cpp:1277
#10 0x03226164 in ThreadWeaver::JobRunHelper::runTheJob (this=0xad39a25c, th=0x9936568, job=0x9f72d90) at ../../../threadweaver/Weaver/Job.cpp:106
#11 0x032264c1 in ThreadWeaver::Job::execute (this=0x9f72d90, th=0x9936568) at ../../../threadweaver/Weaver/Job.cpp:135
#12 0x0322518a in ThreadWeaver::ThreadRunHelper::run (this=0xad39a2e4, parent=0x9937168, th=0x9936568) at ../../../threadweaver/Weaver/Thread.cpp:95
*** Bug 244989 has been marked as a duplicate of this bug. *** *** Bug 245340 has been marked as a duplicate of this bug. *** *** Bug 245484 has been marked as a duplicate of this bug. *** *** Bug 245487 has been marked as a duplicate of this bug. *** Created attachment 49489 [details]
New crash information added by DrKonqi
Hi, I'm attaching my crash to this bug report because both the circumstances and the backtrace appear to be similar. In my case, amarok crashed just after unmounting my USB mp3 player through the device list applet on the panel.
Created attachment 54439 [details]
New crash information added by DrKonqi
amarok (2.4-GIT) on KDE Platform 4.5.4 (KDE 4.5.4) using Qt 4.7.1
- What I was doing when the application crashed:
Removing the USB media device (my Samsung Jet phone, in Mass Storage mode)...
-- Backtrace (Reduced):
#7 0x00007f7acfb95f24 in Handler::UmsReadCapability::setAssociateTrack (this=0x7f7ab8069400, track=...) at /donnees/amarok-git/src/core-impl/collections/umscollection/handler/capabilities/UmsReadCapability.cpp:55
#8 0x00007f7af061b4d1 in Meta::MediaDeviceHandler::privateParseTracks (this=0x17b21c0) at /donnees/amarok-git/src/core-impl/collections/mediadevicecollection/handler/MediaDeviceHandler.cpp:867
#9 0x00007f7af061d8cc in Meta::ParseWorkerThread::run (this=0x2228610) at /donnees/amarok-git/src/core-impl/collections/mediadevicecollection/handler/MediaDeviceHandler.cpp:1304
[...]
#11 0x00007f7aebdd7cce in ThreadWeaver::Job::execute(ThreadWeaver::Thread*) () from /usr/lib/libthreadweaver.so.4
[...]
#13 0x00007f7aebdd7538 in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4
*** Bug 261422 has been marked as a duplicate of this bug. *** (In reply to comment #8) > *** Bug 261422 has been marked as a duplicate of this bug. *** but that crash isn't caused by adding or removing a device. it is triggered even when the device is mounted before launching Amarok, and without removing the device. either that's not a dupe or this bug's title should be changed accordingly. MediaDeviceHandler is given to the thread but no apparent code ensures that the handler is not deleted during the running of the parser thread. This is a bigger change to fix. Is this still valid? Reproducible with Amarok 2.5 I doubt this is reproducible, Handler::UmsReadCapability was removed before 2.5.0. Myriam? Darn, I should have looked better at the backtrace I got. Closing, since the incriminated Handler is not here anymore. Changing NEEDSINFO → RESOLVED so that his doesn't pop in searches. |