| Summary: | Amarok crashed on startup [@ Phonon::Gstreamer::Backend::logMessage] | ||
|---|---|---|---|
| Product: | [Unmaintained] phonon-backend-gstreamer | Reporter: | Daniel Hahler <kde-bugzilla> |
| Component: | general | Assignee: | Harald Sitter <sitter> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | 20120808_bugs.kde.org, adrien.bellanger, aelgali, bga.lambert, buijert, bwoodcock, christopherheiny, darrylbaker57, fosterdave, jcnengel, katoiam, kde-bugzilla, lazor, liquidsky42, martin.sandsmark, mingomax, myriam, paulo.fidalgo.pt, sagiben, stefansnorri, stimut, valorie.zimmerman, W.Strehlow |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.4.4 | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
Daniel Hahler
2010-12-14 04:36:36 UTC
This crash is not reproducible: when starting Amarok again it worked OK. The problem is with the Phonon Gstreamer backend apparently. Closing for now, feel free to report this to Phonon if the bug reappears. Created attachment 54564 [details]
New crash information added by DrKonqi
amarok (2.3.90) on KDE Platform 4.5.85 (4.6 Beta2) using Qt 4.7.0
Happened again, this time during playback (after several hours).
Do you know where Phonon bugs belong? Can you forward it accordingly?
-- Backtrace (Reduced):
#7 Phonon::Gstreamer::Backend::logMessage (this=0x0, message=..., priority=2, obj=0x9a61810) at ../../gstreamer/backend.cpp:469
#8 0xad9a75cc in Phonon::Gstreamer::MediaObject::changeState (this=0x9a61810, newstate=Phonon::ErrorState) at ../../gstreamer/mediaobject.cpp:763
#9 0xad9ad479 in Phonon::Gstreamer::MediaObject::handleBusMessage (this=0x9a61810, message=...) at ../../gstreamer/mediaobject.cpp:1494
#10 0xad99893e in Phonon::Gstreamer::Backend::handleBusMessage (this=0x9d0b2a8, message=...) at ../../gstreamer/backend.cpp:435
#11 0xad9989e9 in Phonon::Gstreamer::Backend::qt_metacall (this=0x9d0b2a8, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xb3be830) at ./moc_backend.cpp:82
You did not by chance switch the phonon backend around the time the crash appeared? Created attachment 54565 [details]
New crash information added by DrKonqi
amarok (2.3.90) on KDE Platform 4.5.85 (4.6 Beta2) using Qt 4.7.0
- What I was doing when the application crashed:
Playing mp3
- Custom settings of the application:
I changed the backend of phonon to use gstreamer instead of XINE
-- Backtrace (Reduced):
#6 Phonon::Gstreamer::Backend::logMessage (this=0x0, message=..., priority=2, obj=0x6c2b30) at ../../gstreamer/backend.cpp:469
#7 0x00007f2e350ece5f in Phonon::Gstreamer::MediaObject::changeState (this=0x6c2b30, newstate=<value optimized out>) at ../../gstreamer/mediaobject.cpp:763
#8 0x00007f2e350f23e1 in Phonon::Gstreamer::MediaObject::handleBusMessage (this=0x6c2b30, message=<value optimized out>) at ../../gstreamer/mediaobject.cpp:1498
#9 0x00007f2e350df5b6 in Phonon::Gstreamer::Backend::qt_metacall (this=0x984a00, _c=<value optimized out>, _id=<value optimized out>, _a=0x20f6380) at ./moc_backend.cpp:82
#10 0x00007f2e4f23cbde in QObject::event (this=0x984a00, e=0x0) at kernel/qobject.cpp:1219
No, Harald, I was not changing the Phonon backend. But I have just tried that, which caused other crashes; see bug 259972 and bug 259973. *** Bug 261356 has been marked as a duplicate of this bug. *** *** Bug 262045 has been marked as a duplicate of this bug. *** *** Bug 262090 has been marked as a duplicate of this bug. *** All possible cases of this crash ought to be fixed in phonon-gstreamer from git master. Soon to be released as 4.4.4. Also it requires phonon from either the 4.4 branch or master. For the record: the ultimate cause for this was that Amarok deletes the MediaObject once Phonon goes into error state. Which depending on the precise situation would either delete the MO while another thread was still working on it, or delete it while there were still pending messages for processing (such as in the initial report). That said, there is still a chance that I missed one case where Amarok pulls away the MO while something else is working on it, however very unlikely. Phonon now only forwards statechanges to the API consumer once the MO returns to the eventloop (i.e. is done with the current task). *** Bug 262240 has been marked as a duplicate of this bug. *** *** Bug 263211 has been marked as a duplicate of this bug. *** *** Bug 263302 has been marked as a duplicate of this bug. *** *** Bug 263471 has been marked as a duplicate of this bug. *** *** Bug 263885 has been marked as a duplicate of this bug. *** *** Bug 264004 has been marked as a duplicate of this bug. *** *** Bug 264305 has been marked as a duplicate of this bug. *** Since I just looked them up. These 3 revisions ought to be fixing this problem with 4.4.3 (in case someone wants to backport them for their distro): * https://projects.kde.org/projects/kdesupport/phonon/phonon/repository/revisions/febb6135f5137bdaafbf9ce7502a5a3a8c264d83 * https://projects.kde.org/projects/kdesupport/phonon/phonon/repository/revisions/ec759e8a39a87a26ef4f047c067492cb16ba5ddc * https://projects.kde.org/projects/kdesupport/phonon/phonon-gstreamer/repository/revisions/0ef1c476ee5cac06c0cc2d5ccad1c5aad2e2408c The first two prevent Amarok from eating the MediaObject while it is still doing things by queuing the signal emission until the MO is done with whatever it is doing. The third prevents crashes from a gstreamer message bus calling back to an already dead MO. *** Bug 264558 has been marked as a duplicate of this bug. *** *** Bug 265172 has been marked as a duplicate of this bug. *** *** Bug 265962 has been marked as a duplicate of this bug. *** *** Bug 267137 has been marked as a duplicate of this bug. *** *** Bug 267506 has been marked as a duplicate of this bug. *** *** Bug 268434 has been marked as a duplicate of this bug. *** *** Bug 269513 has been marked as a duplicate of this bug. *** *** Bug 269514 has been marked as a duplicate of this bug. *** *** Bug 269811 has been marked as a duplicate of this bug. *** reassigning to the new bugzilla product for better bug tracing of the various backends. Sorry for the noise. *** Bug 278273 has been marked as a duplicate of this bug. *** |