Page 1 of 3
Constant 25% CPU usage even video not being played
Posted: Sat Jan 31, 2015 2:09 pm
by Nake
I wrote about this first time into 5.0.0 released announcement post here:
viewtopic.php?p=14589#p14589
There is full quote what I said in above post, if you're too lazy to click it open:
I finished watching an episode of series and I was surfing web with phone at couch when I suddenly realized that my PC was louder than it should've been on idle. So I checked Task Manager and javaw.exe was using 25% of CPU (so it was CPU fan making all the noise). This is new in 5.0.0, never happened with earlier versions before, atleast for me. Unfortunately I rebooted UMS and I didn't remember to take logs to safety. I tried to reproduce this by playing same file for awhile but it didn't work. I make sure to add it next time when/if this happens again.
I have Java 8 Update 31 (32bit & 64bit) installed and I use BubbleUPnP on Nexus 4 (Lollipop 5.0.1) to browse files and to select what I want to watch via Chromecast. OS: Windows 7 64bit
EDIT: I think cause may be thumbnails, because I enabled them after updating to 5.0.0. I'd like to get confirmation for this one if the case is that. Tho dunno why it would take 15min+ to generate all thumbnails, I don't have that many files.
That edit part is not the cause because it still happened after I unchecked thumbnails.
I currently have 2 trace log files from;
5.0.0-Java7:
https://mega.co.nz/#!XosGBKQa!6IMbDv9id ... NyvsvEcmn8
5.0.0-Java8:
https://mega.co.nz/#!Sl9FnRJT!v_M9huIbK ... 8l95KZz4oI
I am working currently on previous version (4.4.0-Java8) trace log file, just need to watch couple episodes first
Re: Constant 25% CPU usage even video not being played
Posted: Sat Jan 31, 2015 11:35 pm
by Nake
Trace debug from UMS 4.4.0-Java8:
https://mega.co.nz/#!mg8FTKrS!V4BpNUr1w ... S7QOr0bDfM
With 4.4.0 that CPU usage don't happen.
Re: Constant 25% CPU usage even video not being played
Posted: Sun Feb 01, 2015 12:53 pm
by SubJunk
Hi Nake, we have reduced the CPU usage in the upcoming version. It shouldn't happen when the program is minimized though.
Re: [Solved] Constant 25% CPU usage even video not being played
Posted: Tue Feb 03, 2015 7:20 am
by jj123
@SubJunk Thanks this is great news, I had raised this in the issue tracker, but it got closed as a "Feature", so I'm really glad the "Feature" got fixed
Re: [Solved] Constant 25% CPU usage even video not being played
Posted: Mon Feb 23, 2015 7:13 am
by Nake
I still have this problem with 5.0.1-Java8 version.
This problem occurs when no files are playing anywhere. For no reason (that I can find), UMS is using 25% CPU after I've stopped watching videos. I didn't remember to snap trace log file, but all necessary information should be on log files at first post. And I already downgraded to 4.4.0-Java8 where I don't have that problem, but if really needed I can install 5.0.1-Java8 again and get logs.
Re: [Solved] Constant 25% CPU usage even video not being played
Posted: Mon Feb 23, 2015 9:35 am
by SubJunk
Hi Nake, does it stop if you minimize UMS? If not, then logs from 5.0.1 would be good
Re: [Solved] Constant 25% CPU usage even video not being played
Posted: Mon Feb 23, 2015 7:25 pm
by Nake
It is minimized (at the tray) 99% of the time. I'll grab those logs and send them here as soon as I have them.
EDIT: Here is the log:
https://mega.co.nz/#!vwM3hRrA!IQQGncGhB ... qqbGgQ7_0I
Re: [Solved] Constant 25% CPU usage even video not being played
Posted: Fri Feb 27, 2015 4:12 am
by Nake
Re: [Solved] Constant 25% CPU usage even video not being played
Posted: Mon Mar 16, 2015 4:32 am
by recognosco
See this 25% CPU usage issue as well. Got the latest 5.0.1 build that is available. The issue says [Solved] how do i fix it?
Re: [Solved] Constant 25% CPU usage even video not being played
Posted: Mon Mar 16, 2015 6:18 am
by Nake
recognosco wrote:See this 25% CPU usage issue as well. Got the latest 5.0.1 build that is available. The issue says [Solved] how do i fix it?
I think SubJunk misunderstood the problem first time as he said it is going to be fixed in 5.0.1 but it wasn't. And after posting logs I haven't heard anything new about the problem. I am currently using 4.4.0 since it doesn't have that problem.