Summary: | [OS X] Crash on exit during CurrentEngine statistics query | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Leo Franchi <lfranchi> |
Component: | Context View | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | lfranchi, stuffcorpse |
Priority: | HI | ||
Version: | 2.3.1-GIT | ||
Target Milestone: | 2.4.0 | ||
Platform: | unspecified | ||
OS: | All | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Leo Franchi
2009-03-18 13:59:46 UTC
SVN commit 941003 by lfranchi: abort queries on destruction. supposed to fix the crash i'm working on, but doesn't. still good practice to clean up in destruction. CCBUG: 187510 M +9 -0 CurrentEngine.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=941003 Any news on this? Leo, did you continue to work on this? Adapted title... I can't reproduce this with current Amarok 2.2-git. Leo, it says all platforms, but isn't this OS X specific? i just reproduced on linux a week or so ago. basically I have to quit amarok in the last 1s or so before the query finishes. I have a large collection (38000 tracks) so the query is sorta slow, total time might be 3-5 seconds. if I quit in the last 1 or so of those, amarok crashes in mysqle code. Any news on this? Changing target Leo, is this still valid? I can't reproduce this here, Amarok 2.2-git Qt 4.5.2, KDE 4.3.3 Leo, any change to get this done for 2.2.2? This could probably be fixed with a loop, checking for Job::isFinished(), and sleeping 100ms for each iteration. I could do that, but I couldn't test it (my collection is too small to trigger this bug). And really, why do I have to do all this shit :) Adding keyword. Changing target. is this stil valid?? This is an automated message from the triager: Amarok 2.4.1 has been released on May 8 already. Could you please upgrade and test if you can still reproduce this bug? Without feedback within a month we will close this bug as resolved. Thank you for your understanding. Closing for lack of feedback. Feel free to reopen if you can still reproduce this with Amarok 2.4.2 beta 1 or later and provide the necessary feedback. Assuming this is fixed. |