07565: If MAME started from Windows Explorer, it can crash depending on circumstances

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07565	Crash/Freeze	Trivial	Always	Feb 15, 2020, 01:39	Feb 15, 2020, 16:49

Tester	Robbbert	View Status	Public	Platform	MAME (Self-compiled)
Assigned To		Resolution	Open	OS	Windows Vista/7/8 (64-bit)
Status [?]	Acknowledged			Driver
Version	0.218	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	07565: If MAME started from Windows Explorer, it can crash depending on circumstances
Description	If you start MAME from Explorer, it will try to send errors to message boxes, because there's no console. If you're in full screen, message boxes don't show, so it tries to switch to windowed mode first, then displays the message box. When answered, MAME should start. But, when MAME tries to switch to windowed mode, it crashes (d3d), or disappears (opengl, bgfx). On GDI, there's no messagebox at all, and mame starts up into the menu.
Steps To Reproduce	1. You must make sure that MAME will produce some kind of error at start. For our purposes, we disabled the sound drivers in the Device Manager. 2. Make sure your mame.ini settings are set with "window 0". 3. In Windows Explorer, double-click mame64.exe to start it. 4. Depending on the video mode, it may crash or disappear, as stated in the description pane above.
Additional Information	If you comment out lines 74 - 79 of winmain.cpp, MAME will start up without error, but any messages that would have gone to the console are lost instead.
Github Commit

Flags
Regression Version
Affected Sets / Systems

Attached Files