Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: mala crash on screensaver  (Read 4437 times)

0 Members and 1 Guest are viewing this topic.

raph

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 73
  • Last login:September 11, 2022, 11:42:35 pm
  • Gradually adding bells and whistles to a stock cab
mala crash on screensaver
« on: August 24, 2015, 03:47:45 am »
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.

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

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 73
  • Last login:September 11, 2022, 11:42:35 pm
  • Gradually adding bells and whistles to a stock cab
Re: mala crash on screensaver
« Reply #1 on: August 24, 2015, 11:52:18 am »
Additional info:

Running Windows 10.

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

raph

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 73
  • Last login:September 11, 2022, 11:42:35 pm
  • Gradually adding bells and whistles to a stock cab
Re: mala crash on screensaver
« Reply #2 on: August 24, 2015, 11:10:59 pm »
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: [Select]
Run FlipSS.exe /off
RunWait D:\Frontends\MaLa\MaLa174\mala.exe
Run FlipSS.exe /on
ExitApp

I'd still love any insight anyone has.

raph

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 73
  • Last login:September 11, 2022, 11:42:35 pm
  • Gradually adding bells and whistles to a stock cab
Re: mala crash on screensaver
« Reply #3 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.

loadman

  • Moderator
  • Trade Count: (+3)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4305
  • Last login:August 17, 2020, 03:23:55 am
  • Cocktail Cab owner and MaLa FE developer
    • MaLa
Re: mala crash on screensaver
« Reply #4 on: May 19, 2017, 02:31:44 am »
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.
Thanks for the feedback

Ho many images set it over the limit?

raph

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 73
  • Last login:September 11, 2022, 11:42:35 pm
  • Gradually adding bells and whistles to a stock cab
Re: mala crash on screensaver
« Reply #5 on: May 19, 2017, 03:14:50 am »
It was the MAME snap directory; I have a couple of these for different versions, and the one with 29k images definitely did it. I think so did the one with 10k, though.

The one that works OK is my menu_snaps folder, used for snaps for the menus only, and it only has 159 in it.

 I haven't tried doing incremental tests, but I could if it would help. A binary search to find the tipping point would be tedious, but wouldn't take THAT long.

From watching it happen, I suspect it is something as simple as building the list of filenames to choose from, just taking too long.