Summary: | using device notification to mount usbpen results in 100% cpu usage | ||
---|---|---|---|
Product: | [Frameworks and Libraries] solid | Reporter: | Patrizio Bassi <patrizio.bassi> |
Component: | libsolid-fstab | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | afiestas, lukas, plasma-bugs, wilderkde |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Patrizio Bassi
2010-12-27 12:09:49 UTC
I can reproduce occasional instances of kded4 eating 100% cpu, but I can't find any correlation with mounting/unmounting an usbpen. Can you confirm it happens most of the times you mount an usbpen with the device notifier? If it is the case could you please try mounting the same usbpen with dolphin and see if it triggers the same problem? Thanks __J I can reproduce occasional instances of kded4 eating 100% cpu, but I can't find any correlation with mounting/unmounting an usbpen. Can you confirm it happens most of the times you mount an usbpen with the device notifier? If it is the case could you please try mounting the same usbpen with dolphin and see if it triggers the same problem? Thanks __J Perhaps related to #261200? i'm starting to think it's related to https://bugs.kde.org/show_bug.cgi?id=261463 i will try to reproduce later: when dolphin is stuck as the bug reports, if the notificator tries to mount and raise a new dolphin instance it may enter this loop. When it happens, would you mind attaching gdb to kded4 and see what's going on there? thanks It deadlocks in the fstab backend, investigating; I also got Dolphin hung up, as described in bug #261463 Any new on this? has anybody been able to reproduce this? Duplicated bugs were fixed. Closing this one. If it is not a duplicate and you still can reproduce it, please feel free to reopen ! *** This bug has been marked as a duplicate of bug 261463 *** |