| Summary: | Amarok crashes while searching in a large music library | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Jörn Schönyan <joern.schoenyan> |
| Component: | general | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | justin.zobel |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 2.8.0 | ||
| Target Milestone: | 2.9 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Jörn Schönyan
2014-04-21 11:02:26 UTC
What exactly did you do when the crash happened? We can test with large collections, I can't reproduce this here at all with a collection of about 60'000 titles Hello Myriam, hope you had a nice easter weekend :-) Well, of roundabout 10+ crashes that day (we played music ~16 hours), I personally just saw one or two. My buddy told me, it happened while just searching. After reopening Amarok, searching again worked fine, even with the same keywords. Anything else I could help with? Thank you, Jörn, it was nice, hope it also was for you :) Where is the collection located? if it is not local but on a remote share that might be the problem, as the connection can time out, but it should be possible to handle this on the system level to avoid time-outs. Oh forgot to mention that, it was on an external HDD (USB3). Then it could be related to when the HD spins down, I had that quite often with an USB disk. But it shouldn't crash, instead provide an error message. Thanks a lot for the fast feedback! Thank you for the crash reports. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |