Summary: | Dolphin crash non stop | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | stars |
Component: | general | Assignee: | Peter Penz <peter.penz19> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | frank78ac, sebastian, trueg |
Priority: | NOR | ||
Version: | 16.12.2 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
stars
2010-05-02 02:01:18 UTC
Thanks for the bug report! This is probably related to a lot of other recent reports on Kubuntu 10.04. If this crash annoys you too much, disabling Nepomuk in the System Settings might be a temporary workaround. @Peter, Sebastian: This backtrace is quite remarkable because it has an enormous number of KLoadMetaDataThreads. @Frank: I think I can explain the enormous number of KLoadMetaDataThreads. If an item is hovered for >= 300 ms, a new thread is created which receives the meta data. A running thread will never be killed, it only gets the hint "you're obsolete - finish yourself as soon as possible". This works fine usually: The hint to "you're obsolete" can be handled very fast by the thread and there are only very rare situations, where 2 threads are alive in parallel. Now having multiple threads in parallel can only happen if: - A hovering over several items is done quite slowly (>= 300 ms per item) - and each thread is blocked (like this seems to be the case above because of the mutex) I've done local changes to test how Dolphin behaves if each thread blocks for 10 seconds and everything works fine: Obsolete threads get ignored, the user interface does not block. So it seems we have the same issue here as the other reported problems, just with more threads :-) I'm running Kubuntu 10.04 with KDE SC 4.5.0 and did no observe this crash. Please reopen the report if it still occurs in your environment. |