Version: 2.4-GIT (using Devel) OS: Linux I have collection stored on SD card and encrypted by the encfs. After upgrade to KDE 4.8 (beta1/beta2) I've noticed, that the encfs process has a high cpu load. It is between 20-40%. Amarok is only one application usin the encrypted directory. Does not mater whether amarok is playing music or not. When I quit Amarok, encfs process again uses 0%. Other application, like (s)mplayer does not triggers it. CPU usage of the encfs process is 0-1% during playing. I think it could be connected with some KIO changes. I did not noticed it in KDE 4.7. Reproducible: Always Steps to Reproduce: 1) Store collection on encfs disk 2) Start Amarok - collection is loaded, collection scanner is not running 3) Check cpu usage of encfs process Actual Results: CPU usage of the encfs process is 20-40% Expected Results: CPU usage of the encfs process will be 0-1% as in other applications. $ amarok -v Qt: 4.7.4 KDE Development Platform: 4.7.90 (4.8 Beta2 (4.7.90) Amarok: 2.4-GIT
Pushing to kdelibs, I very much doubt that this is Amarok related.
I recently updated to 4.8 RC2. The situation is the same. Interesting is that in some cases, encfs is not using so many cpu. I need to start and stop amarok several times and with some special condition, the encfs cpu usage increase only to 3-5%. Note that sometime I have to kill amarok - it does not react on quit command. I also looked to timing. When I start amarok, encfs has 0-1% cpu usage, but after a while (5-10 seconds), something happen and encfs cpu usage increases to 20-30%
I've upgraded to final 4.8 release, compiled latest amarok git source, but situation still the same. Maybe it could be connected somehow with issue that I amarok does not quit completely. When I choose Quit amarok, the icon disappear from the system tray, but amarok is still running - the music is played. I have to kill it with -9 signal. Theses bugs causes I've to switch to clementine, but I like amarok much more and I want to use it again. Please give me some hint, how to trace the reason. I tried strace on amarok and encfs, but there was nothing interesting.
I've unchecked the "Watch folders for the changes" option and there is no issues with encfs cpu usage now. So the problem will be probably there.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. 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!