Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|06148||Crash/Freeze||Critical (emulator)||Always||Mar 3, 2016, 21:16||3 days ago|
|Version||0.171||Fixed in Version||Build||64-bit|
|Summary||06148: daytona: Segmentation Fault|
|Description||daytona will segfault during the second loop of attract mode.|
|Steps To Reproduce||Boot, wait.|
Clones not tested.
Gameplay causes MAME to hardlock shortly after the game hands control to the player.
|Affected Sets / Systems||daytona|
0000.png (67,354 bytes) Mar 3, 2016, 21:34 Uploaded by Tafoid
0.171 Snapshot just before Exception/Crash
|There are no relationsihp linked to this issue.|
Mar 3, 2016, 21:32
Took a snapshot a moment before it crashes with the following stack crawl
Mar 4, 2016, 10:59
|I went as far back as 0.131 and it was already happening. Don't have older builds at hand to find regression version.|
Mar 18, 2017, 09:14
|Daytona doesn't crashed when you set in menu 'GAME SYSTEM' - 'LINK ID' -> to SINGLE with keys F2 and 9.|
15 days ago
|As of MAME 0.192, it will do one of two things after displaying the game settings, either segfault or hardlock MAME.|
3 days ago
This happens before crash or freeze.
Direct3D: resetting device Direct3D: Initialize HLSL Direct3D: Unable to find D3DXCreateEffectFromFileW