Summary: | Amarok2 Crashed While Import Amarok1.4 statistics [@ Amarok::TrayIcon::setupMenu] | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Duncan Clough <duncan.clough+kde> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | fabio.fabbris, jay.flaming, mtadeunet, saft-socke |
Priority: | NOR | ||
Version: | 2.3.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 2.3.2 | |
Sentry Crash Report: | |||
Attachments: |
Debug output for amarok crashing during statistics import
Debug output for amarok crashing during statistics import |
Description
Duncan Clough
2010-05-03 22:34:53 UTC
Another one of those App::notify crashes no one knows how to fix... I did some further testing. Facts: The crash only happens if I do not stay at the bottom of the import progress information window. When I scroll up the window or stop at a particular line (ie a small upward scroll) to read something, if I don't quickly move back to the bottom of the import output, the crash will eventually happen. If I make sure that the cursor/window always remains at the bottom of the import output then I experience no crash and the statistics are imported. Although there are some issues with the actual imported data I don't think this is part of this specific problem. Suggestions: It feels like delay is the result of some storage space/buffer filling up with the import output and when that space fills up amarok crashes. *** Bug 238040 has been marked as a duplicate of this bug. *** *** Bug 238174 has been marked as a duplicate of this bug. *** *** Bug 238620 has been marked as a duplicate of this bug. *** Duncan, could you also post amarok debug output (~last 2/3 screens of it) prior to the crash? You can use following command: amarok --debug > amarok-debug.txt 2>&1 I'm investigating the crash and it seems that it is connected to importer directly calling methods of objects living in different threads. I haven't yet been able to test this in on the same computer that I used to report this bug, since I didn't want to interfere with my Amarok 1.4.10 installation (Amarok 2 still isn't quite there yet, but getting very close). I should be able to test this on the weekend. That said, I tried to recreate this error on another up-to-date Lucid Lynx machine. I installed Amarok 2.3.0 from the Lucid repository and copied my MySQL database across. I could not recreate the crash. The data import (from MySQL to both SQLite and MySQL) also successful - previously there had been errors. I also tried to recreate this error (earlier today, before your post) on another up-to-date Lucid machine that had a fresh install of Amarok 2.3.1. I was unable to do so again. I'd previously experienced this problem on this machine as well, but with an earlier version of Amarok (2.0 or 2.1) when the machine was still running Jaunty. It seems that the updates (OS and Amarok, if there were any) since I last tried to recreate this problem have fixed it/changed its nature. I installed Amarok 2.3.0 from the Ubuntu 10.04 repository on the computer from which I originally reported this bug. It no longer crashed when importing the Amarok 1.4.10 statistics. No matter what I try, I can't reproduce this bug any more. Maybe it was related to something else that has been fixed? The statistics themselves get imported, but then are lost when a "Collection Folder" is manually selected. But I'll file another bug report relating to that... Created attachment 48012 [details]
Debug output for amarok crashing during statistics import
Created attachment 48013 [details]
Debug output for amarok crashing during statistics import
While trying to gather information to report the bug I mentioned above, Amarok crashed while importing statistics. So the the bug is still there after all. The trick -> play music while trying to import and it crashes. Steps: 1. Open Amarok 2. Play Song 3. Settings > Configure Amarok > Collection > Import Statistics 4. Fill out info for MySQL Amarok 1.4 database 5. Click next 6. Crash I reproduced this crash 4 times in a row. The debug output requested by Matěj Laitl has been attached - it is from the 2nd and 3rd crashes. The import happens successfully if Amarok isn't playing music. Confirmed by duplicates. Duncan, much thanks for your feedback. The crash seems to be unrelated to the behaviour I've seen. Therefore, unfortunately, I have no clue how to solve it. Regards, Matěj *** Bug 242558 has been marked as a duplicate of this bug. *** I reported bug: https://bugs.kde.org/show_bug.cgi?id=242558, which has been marked as a duplicate of this bug. I'm getting the same result using the itunes database import option, rather than amarok 1.4, but I don't think it has anything to do with whether I'm playing music or not. For one thing, it will often import hundreds of tracks before crashing, during which time I'm obviously not starting and stopping playback. So either mine's not a duplicate of this, or else the play state is not a factor. Jay, the backtrace is the same, so the bug is the same. Is this still valid for Amarok 2.3.1? I don't have a 1.4 database to test with. This was still valid for 2.3.1 when I tested it. However, I downloaded 2.3.2 Beta 1 (2.3.1.90) earlier this week and have been unable to recreate the bug. I am able to provide you with a 1.4 MySQL database with should you still want to test, but since you won't have the physical music, there might be some issues. I trust you on this, don't worry. Closing as fixed, feel free to reopen if you can reproduce this with 2.3.1.90 or later. |