Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
04201 Crash/Freeze Critical (emulator) Always Jan 24, 2011, 18:39 Feb 9, 2013, 14:22
Tester Tafoid View Status Public Platform MAME (Self-compiled)
Assigned To Resolution Fixed OS
Status [?] Resolved Driver
Version 0.141u1 Fixed in Version Build Normal
Fixed in Git Commit Github Pull Request #
Summary 04201: kinst2, kinst213: Crash using -str 3
Description For some reason, using a -str 3 run on this set causes a crash. I can't seem to trigger it any other way or different length of time.

Program received signal SIGSEGV, Segmentation fault.
0x01b3447d in resource_pool::remove (this=0x0, ptr=0x14cea698)
    at src/emu/emualloc.c:292
292 osd_lock_acquire(m_listlock);
Steps To Reproduce
Additional Information
Github Commit
Flags
Regression Version 0.141u1
Affected Sets / Systems kinst2, kinst213
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
6
User avatar
No.07262
hap
Developer
Feb 23, 2011, 19:29
regression revision: r11027
"C++-ified drcfe and the associated frontends. You now create a
frontend by deriving from drc_frontend and implementing the
describe method."

btw, it will also crash if you exit MAME manually right after the beep.
User avatar
No.07482
Tafoid
Administrator
May 30, 2011, 20:45
edited on: May 30, 2011, 20:45
Added a current build stack crawl (newest tools):
-----------------------------------------------------
Exception at EIP=0250F465 (resource_pool::remove(void*)+0x0013): ACCESS VIOLATION
While attempting to read memory at 00000004
-----------------------------------------------------
EAX=00000000 EBX=1D150864 ECX=000000B7 EDX=1D1707FC
ESI=00000004 EDI=003F25C8 EBP=0022EA08 ESP=0022E9E0
-----------------------------------------------------
Stack crawl:
  0022EA08: 0250F465 (resource_pool::remove(void*)+0x0013)
  0022EA28: 02BA5019 (simple_list<opcode_desc>::remove(opcode_desc&)+0x002d)
  0022EA48: 02BA4F01 (simple_list<opcode_desc>::reset()+0x001d)
  0022EAC8: 02BA516C (simple_list<opcode_desc>::~simple_list()+0x0050)
  0022EAE8: 02BA2064 (opcode_desc::~opcode_desc()+0x0014)
  0022EB68: 02D40A7F (resource_pool_object<opcode_desc>::~resource_pool_object()+0x0063)
  0022EB98: 0250F522 (resource_pool::remove(void*)+0x00d0)
  0022EBB8: 02BA5019 (simple_list<opcode_desc>::remove(opcode_desc&)+0x002d)
  0022EBD8: 02BA4F01 (simple_list<opcode_desc>::reset()+0x001d)
  0022EC58: 02BA516C (simple_list<opcode_desc>::~simple_list()+0x0050)
  0022EC78: 02CFD645 (fixed_allocator<opcode_desc>::~fixed_allocator()+0x0011)
  0022ED08: 0247E3D0 (drc_frontend::~drc_frontend()+0x00b8)
  0022ED88: 02CD34FC (mips3_frontend::~mips3_frontend()+0x0050)
  0022EE08: 02DE2E6B (resource_pool_object<mips3_frontend>::~resource_pool_object()+0x0067)
  0022EE38: 0250F522 (resource_pool::remove(void*)+0x00d0)
  0022EE68: 022DFE36 (cpu_exit_mips3(legacy_cpu_device*)+0x004b)
  0022EE88: 0280F55E (legacy_cpu_device::device_stop()+0x0032)
  0022EEB8: 0254287F (device_t::stop()+0x004f)
  0022EEE8: 02540513 (device_list::stop_all()+0x0021)
  0022EF08: 0254070A (device_list::exit()+0x003c)
  0022EF28: 02F08BEB (delegate_base<void, _noparam, _noparam, _noparam, _noparam>::operator()() const+0x0017)
  0022EF58: 0251BCF3 (running_machine::call_notifiers(machine_notification)+0x0039)
  0022F058: 0251ADF6 (running_machine::run(bool)+0x06a6)
  0022F9A8: 0254B8D0 (mame_execute(emu_options&, sd_interface&)+0x0205)
  0022FB58: 027F48F5 (cli_frontend::execute(int, char**)+0x0365)
  0022FEC8: 01E12A51 (utf8_main(int, char**)+0x01ad)
  0022FEF8: 02A08AFA (wmain+0x008a)
  0022FFC0: 00401422 (__tmainCRTStartup+0x0292)
  0022FFF0: 7C817077 (RegisterWaitForInputIdle+0x0049)
User avatar
No.08918
Firewave
Senior Tester
Sep 20, 2012, 08:21
I don't get a crash in 0.147
User avatar
No.08926
hap
Developer
Sep 20, 2012, 09:41
edited on: Sep 20, 2012, 09:47
I can still make it crash (64bit, mingw, vanilla).

blue screen --> red screen --> black screen and nintendo logo
I press ESC to exit MAME, just as the screen turns from red to black, then it crashes 1 out of 3 times I try it.
I can also make it crash sometimes by exiting right before the red screen.
User avatar
No.08927
Firewave
Senior Tester
Sep 20, 2012, 10:30
My bad. I accidentally tested kinst. Can reproduce it.
User avatar
No.09322
Firewave
Senior Tester
Feb 9, 2013, 14:22
Only kinst213 crashes for me and only on Windows with -str 3.