Summary: | [kdirmodel] lokalize makes lots of kioslave.exe | ||
---|---|---|---|
Product: | [Applications] lokalize | Reporter: | Viesturs Zarins <viesturs.zarins> |
Component: | general | Assignee: | Nick Shaforostoff <shafff> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | elchevive, freekdekruijf, sdepiets |
Priority: | NOR | Keywords: | investigated, triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: |
Description
Viesturs Zarins
2009-01-28 10:09:44 UTC
did you check dolphin against kioslave.exe spam? Dolphin keeps down to humble 4 kioslaves, even after using it for about 10 mins. And they all terminate in about 1 min time after dolphin is closed. With lokalize they keep running forever. After using Lokalize for about 10 mins, my 2 Gb of ram is filled up with more than 100 kioslves, 16 Mb each. I disabled every Lokalize feature I could find and ended up with this: * saving does not leak kioslaves * just moving trough strings in a file leaks kioslaves. Even when the TM toolview is closed. * Translation Memeory search (F7) does not leak kioslaves * adding folder to TM slowly and irregularely leaks kioslaves over time (as the files get scanned?). >just moving trough strings in a file leaks kioslaves.
Thanks. At least that makes a start point for me to investigate.
Hi, Still present on kde 4.4.0. Seems that when Lokalize is loading the project view it creates a lot of kioslaves.exe Regards, Luiz I can add that lokalize generates an abnormal amount of messages in .xsession-errors. After leaving my system for a few hours I found it back with a full disk and the above file of 10GB. I do have a copy of the file with this name of 301 MB, which can be made available. Most of the errors are from lokalize. I commented most of the kDebug() strings in jobs.cpp, so 4.4.3 will be less verbose. With the new nightly builds from Craft I can't reproduce the issue on Windows. Let me know if you can still reproduce. This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change. |