INTERACT FORUM

More => Old Versions => JRiver Media Center 26 for Linux => Topic started by: tlenthe on February 24, 2020, 10:54:02 am

Title: MC 26.0.26 (64 bit) - excessive CPU usage
Post by: tlenthe on February 24, 2020, 10:54:02 am
On initial startup, it is working fine (Ubuntu 18.04 with latest patches), but once the DSP window is opened (either by clicking on gear icon or through options window, CPU usage increases (to about 10% of total) and response time so slow as to become unusable.  Only fix seems to be wait for slow response to close app normally or use process kill switch.  Doesn't occur when just opening options window as long as DSP settings not entered.

DSP window is very slow to paint, starting with selection items in two right columns, followed by bottom items, and lastly left-hand column.  At very end, background is painted around selection items.
Title: Re: MC 26.0.26 (64 bit) - excessive CPU usage
Post by: alessandro on February 26, 2020, 02:15:20 pm
Confirm all thread, need to mount again MC 25.114 for now
Title: Re: MC 26.0.26 (64 bit) - excessive CPU usage
Post by: vma on February 27, 2020, 12:49:44 am
I have similar experience - Debian Buster on the NUC i3 computer. Process Xorg about 10%, slow response with DSP window, slow response closing MC26.
Title: Re: MC 26.0.26 (64 bit) - excessive CPU usage
Post by: vma on February 27, 2020, 07:36:26 am
MC25.0.114 has no problems. Screen Tools - Options - DSP is OK, quick responses, Xorg about 1%.
Title: Re: MC 26.0.26 (64 bit) - excessive CPU usage
Post by: bob on February 27, 2020, 02:57:41 pm
Not able to reproduce this on debian 8 with xfce.
Please check https://yabb.jriver.com/interact/index.php/topic,124263.msg860869.html#msg860869

Then report back what Desktop and Window manager you are using.
Title: Re: MC 26.0.26 (64 bit) - excessive CPU usage
Post by: vma on February 27, 2020, 03:12:34 pm
Operating System: Debian GNU/Linux 10
KDE Plasma Version: 5.14.5
Qt Version: 5.11.3
KDE Frameworks Version: 5.54.0
Kernel Version: 4.19.0-8-amd64
OS Type: 64-bit
Processors: 2 × Intel® Core™ i3-8109U CPU @ 3.00GHz
Memory: 7,7 GiB of RAM
Title: Re: MC 26.0.26 (64 bit) - excessive CPU usage
Post by: bob on February 27, 2020, 03:22:41 pm
Operating System: Debian GNU/Linux 10
KDE Plasma Version: 5.14.5
Qt Version: 5.11.3
KDE Frameworks Version: 5.54.0
Kernel Version: 4.19.0-8-amd64
OS Type: 64-bit
Processors: 2 × Intel® Core™ i3-8109U CPU @ 3.00GHz
Memory: 7,7 GiB of RAM
Thanks.
Did you try the 26.0.23 build linked in the thread linked above?
Do you notice a fight for focus between MC and another app on the desktop?
Title: Re: MC 26.0.26 (64 bit) - excessive CPU usage
Post by: vma on February 28, 2020, 07:58:23 am
Version 26.0.23 is OK. No delays. Xorg 1%.
Title: Re: MC 26.0.26 (64 bit) - excessive CPU usage
Post by: bob on February 28, 2020, 12:24:56 pm
Version 26.0.23 is OK. No delays. Xorg 1%.
Ok, sent you a PM...
Title: Re: MC 26.0.26 (64 bit) - excessive CPU usage
Post by: bob on February 28, 2020, 01:56:23 pm
Also on your plasma desktop check:
System Settings->Window Behavior->Focus Stealing Prevention
It should be set to
None
Title: Re: MC 26.0.26 (64 bit) - excessive CPU usage
Post by: vma on February 28, 2020, 02:10:05 pm
Bob, thank you. I installed it and tried what you told me. The result:
Focus Stealing Prevention - None to Medium is OK, High and Extreme I cannot enter any Menu Item.
Title: Re: MC 26.0.26 (64 bit) - excessive CPU usage
Post by: bob on February 28, 2020, 04:46:18 pm
Bob, thank you. I installed it and tried what you told me. The result:
Focus Stealing Prevention - None to Medium is OK, High and Extreme I cannot enter any Menu Item.
It really should be set to none. It's a hack for misbehaving apps.
Did that build and setting solve the CPU use issue?
Title: Re: MC 26.0.26 (64 bit) - excessive CPU usage
Post by: vma on February 28, 2020, 09:46:59 pm
It really should be set to none. It's a hack for misbehaving apps.
Did that build and setting solve the CPU use issue?

YES. Thank you.
Title: Re: MC 26.0.26 (64 bit) - excessive CPU usage
Post by: RemyJ on March 01, 2020, 11:10:10 am
It really should be set to none. It's a hack for misbehaving apps.
An app that requires it to be turned off could also be considered to be "misbehaving".  :)