Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
04117 Speed Major Always Nov 11, 2010, 00:44 Dec 18, 2018, 21:15
Tester Tafoid View Status Public Platform MAME (Self-compiled)
Assigned To Resolution Open OS Windows XP (32-bit)
Status [?] Confirmed Driver mhavoc.cpp
Version 0.140u1 Fixed in Version Build Normal
Summary 04117: mhavocp: [possible] Increasing slowdown in Test Mode
Description When you enter test mode (F2), the emulation speed slowly gets worse and worse and worse. If you keep it at skip 0, you'll eventually see it drop all by itself.

Problem is, it's a prototype game and I'm unsure if it's supposed to do that or not. Nothing but that white border has ever showed up for test mode on the prototype rom. Older MAME versions did not have this severe slowdown, however.
Steps To Reproduce
Additional Information
Flags Possible
Regression Version 0.108u5
Affected Sets / Systems mhavocp
Attached Files
There are no relationship linked to this issue.
User avatar
Nov 11, 2010, 16:46
It slows down when I hit the F2 key but it doesn't looks like getting worse for me.
If I disable speed throttle, the normal game mode works at 600 - 700% with no frame skip, and in the test mode, it is around 500% - 550%.
User avatar
Nov 11, 2010, 17:16
edited on: Nov 11, 2010, 17:17
I should try a 64-bit build. This is on a 32-bit build on XP. Odd that you are not able to duplicate it.. Does the same thing for me on all tested builds since 0.108u5.
User avatar
Nov 12, 2010, 09:14
It reproduced on XP here. It gets slower little by little, and with -nomt it became stable around 40% - 50%. And with -mt, it almost eats up CPU power and the frame rate is around 19%.
User avatar
Senior Tester
Dec 18, 2018, 15:33
Tested on mame 0.140 and mame 0.204
Not happening on windows 7 64-bit
User avatar
Dec 18, 2018, 21:15
Tested here on win7 64-bit with current git (32-bit build). Pressing F2 firstly causes a small freeze, followed by the white rectange. After about 30 sec, the % counter ran down to 70% where it stabilised.

So, the problem is still there.

Task Manager shows MAME taking 4% CPU and 56,664K of RAM. While the Task Manager is showing, the rate rises to 71%.