pc issue Major bug: MX 5.1.4.2100 keeps monitor(s) from entering stand-by mode

[phoenix-76 29]

Hello, I noticed a nasty bug linked to the recent MX 5.1.4.2100 release - my LCD screens won't go off after time specified in OS power management settings. I rolled back to several previous MX5 releases to see if I can reproduce the problem and the result is the problem clearly follows only the recent 5.1.4.2100 release.

How to duplicate:
1. Launch MX5 with QuickAccess background set to animated picture.
2. Start elevated command prompt with admin privileges.
3. Type in "powercfg -requests".
4. Verify content of DISPLAY and SYSTEM sections.

=> With MX 5.1.4.1700 or any older MX 5.1.4.x release there are no display or system resources occupied (see the first screnshot MX 5.1.4.1700.jpg), on the other hand MX 5.1.4.2100 seems to utilize video and audio playback resources all the time even when no multimedia content is active (see the second screenshot MX 5.1.4.2100.jpg).

Thanks to prioritize resolution of this problem. Until this is fixed, the obvious workaround for me is to roll back to 5.1.4.1700.
 

OS: Windows 10 Home 64-bit, version 1709, build 16299.125
Video card: NVIDIA GeForce GTX 760 (discrete)
Sound card: Soundblaster ZxR (discrete)
Other: dual-monitor setup, 16 GB RAM, i5 CPU

[pantantrollo 130]

No problem here with v.2100 (portable)

 

 

[phoenix-76 29]

I noticed there's been 5.1.4.2400 version released over night. Unfortunately, the issue is still there and it's specific to 5.1.4.2100 and 5.1.4.2400 releases only.

[PHYR 471]

2 hours ago, phoenix-76 said:

I noticed there's been 5.1.4.2400 version released over night. Unfortunately, the issue is still there and it's specific to 5.1.4.2100 and 5.1.4.2400 releases only.

Don't know why you are having this issue

Edit The most recent releases of M5 introduced hardware boost in advanced options, perhaps this is affecting you somehow? Although having hardware boost enabled or not didn't affect my results.

With M5 running, I had no issue with it affecting when the screen turned off, sleep or hibernate were also not affected. I'm on win10b17046.

[phoenix-76 29]

Hello, I still need to confirm this on my primary system later today, but I've just probably narrowed down root cause of the problem to the animated QuickAccess background! Once I change the background to any still image and restart the browser the issue immediately goes away. Any chance anyone could confirm this as a generic bug please?

I noticed significant improvement in loading the QA background in 5.1.4.2100, now it appears though that this power boost mentioned by PHYR comes at the cost of this nasty side effect of suppressing local OS power management settings.

[7twenty 1,226]

As with PHYR, 5.1.4.2100 portable, all show none.

[phoenix-76 29]

PHYR / 7twenty, thanks for your comments. Would you please try to set QA background to one of the animated pictures, restart the browser and see if you can reproduce my findings? On my side the problem is 100% reproducible with both installed and portable versions, even when not logged to my MX account. Once I revert to static image background, the problem disappears. Once I set the animated background again, the resource hog is immediately back.

[pantantrollo 130]

5 hours ago, phoenix-76 said:

PHYR / 7twenty, thanks for your comments. Would you please try to set QA background to one of the animated pictures, restart the browser and see if you can reproduce my findings? On my side the problem is 100% reproducible with both installed and portable versions, even when not logged to my MX account. Once I revert to static image background, the problem disappears. Once I set the animated background again, the resource hog is immediately back.

Yes, it's the animated background. (last beta v.2400 Portable)

[7twenty 1,226]

18 hours ago, phoenix-76 said:

set QA background to one of the animated pictures,

Sorry, missed that part. Can confirm that Display and System show a device in use if it's the current tab. Only System (Audio) if the tab isn't in focus.

[phoenix-76 29]

Just for the record, the problem persists with 5.1.4.3000.

[Nickitt＠タガタメ＆アズレン舞鶴 0]

I have the same problem,even with 5.1.5 > <