Front End Support > MaLa Frontend

mala crash on screensaver

(1/2) > >>

raph:
Mala is reliably crashing when the screensaver kicks in. It doesn't matter if it is the Mala built in one, or the Windows ones -- and it doesn't matter which Windows one it is.

The symptom is that it pops exception dialogs repeatedly multiple times a second, until manually killed:


--- Quote ---2015/08/24  00:28:43.10   Debug **: WMPOWERBROADCAST: Received Screen Saver start message
2015/08/24  00:28:43.15   Error: Exception Message: System Error.  Code: 5.
Access is denied, Object Function: AppDeactivate, Exception Class: EOSError, Object Class: TTimer
2015/08/24  00:28:43.21   Error: Exception Message: System Error.  Code: 5.
Access is denied, Object Function: AppDeactivate, Exception Class: EOSError, Object Class: TTimer
2015/08/24  00:28:43.27   Error: Exception Message: System Error.  Code: 5.
Access is denied, Object Function: AppDeactivate, Exception Class: EOSError, Object Class: TTimer
2015/08/24  00:28:43.34   Error: Exception Message: System Error.  Code: 5.
Access is denied, Object Function: AppDeactivate, Exception Class: EOSError, Object Class: TTimer
2015/08/24  00:28:43.40   Error: Exception Message: System Error.  Code: 5.
Access is denied, Object Function: AppDeactivate, Exception Class: EOSError, Object Class: TTimer
2015/08/24  00:28:43.46   Error: Exception Message: System Error.  Code: 5.
Access is denied, Object Function: AppDeactivate, Exception Class: EOSError, Object Class: TTimer
2015/08/24  00:28:43.52   Error: Exception Message: System Error.  Code: 5.
Access is denied, Object Function: AppDeactivate, Exception Class: EOSError, Object Class: TTimer
2015/08/24  00:28:43.58   Error: Exception Message: System Error.  Code: 5.
Access is denied, Object Function: AppDeactivate, Exception Class: EOSError, Object Class: TTimer
2015/08/24  00:28:43.65   Error: Exception Message: System Error.  Code: 5.
Access is denied, Object Function: AppDeactivate, Exception Class: EOSError, Object Class: TTimer
2015/08/24  00:28:43.71   Error: Exception Message: System Error.  Code: 5.
Access is denied, Object Function: AppDeactivate, Exception Class: EOSError, Object Class: TTimer
2015/08/24  00:28:43.77   Error: Exception Message: System Error.  Code: 5.
Access is denied, Object Function: AppDeactivate, Exception Class: EOSError, Object Class: TTimer
2015/08/24  00:28:43.84   Error: Exception Message: System Error.  Code: 5.
Access is denied, Object Function: AppDeactivate, Exception Class: EOSError, Object Class: TTimer
2015/08/24  00:28:43.90   Error: Exception Message: System Error.  Code: 5.

--- End quote ---

Running no screensaver and using power options to turn off the monitors instead seems to work, but I would rather not do that as one of my monitors (the marquee one) displays "no sync" rather than going blank.

Alternatively, I could just not leave mala running. :(

I've tried both Mala174 and the beta, same effect.

raph:
Additional info:

Running Windows 10.

Doesn't matter if it compatibility mode for Win 7, Win 8, or whether run as administrator.

raph:
My interim workaround is to use AHK to turn off the screensaver when Mala launches, with this little utility: http://www.jddesign.co.uk/products/freeware/freeware_programs.htm#FlipSS

I then turn it back on on program exit.

Basically,


--- Code: ---Run FlipSS.exe /off
RunWait D:\Frontends\MaLa\MaLa174\mala.exe
Run FlipSS.exe /on
ExitApp

--- End code ---

I'd still love any insight anyone has.

raph:
It's been years, but: it turns out that I was recently able to get the MaLa screensaver to work by pointing it at a directory with way fewer images in it.

loadman:

--- Quote from: raph on April 24, 2017, 11:51:25 pm ---It's been years, but: it turns out that I was recently able to get the MaLa screensaver to work by pointing it at a directory with way fewer images in it.

--- End quote ---
Thanks for the feedback

Ho many images set it over the limit?

Navigation

[0] Message Index

[#] Next page