 No.18548
Tafoid Administrator
Mar 14, 2021, 23:45
|
Known. Issue with compiling with certain GCC's apparently Just drop the -verbose |
|---|---|
|
No.18550
Tafoid Administrator
Mar 15, 2021, 04:14
|
I've reopened. The crash reported is similar to the one we've been getting with -verbose. I've tried to duplicate and I cannot get anything at all to crash - using your string and just changing the rompath to match mine. Can you try adding -norc (no read config) to your string or try running in a freshly installed folder the release version of MAME from mamedev.org? You could have version mismatched bgfx file or something else? Perhaps other people can try to duplicate? |
 No.18551
Andrew Tester
Mar 15, 2021, 05:05
edited on: Mar 15, 2021, 12:56
|
I deleted everything in my MAME folder and installed a fresh 0.229. I used this command line run from my MAME folder E:\emulator-mame>mame diehard -norc -rompath e:\arcade -video bgfx -bgfx_backend d3d12 and it resulted in a crash after the "CART 1" message was displayed. With subsequent runs, emulation gets past that and crashes after the patents notice is displayed. I then renamed my MAME executable to mame229 and downloaded the Git MAME to the folder and get the same result. |
 No.18560
Osso Moderator
Mar 15, 2021, 20:15
|
Getting the following using the command line from the most recent comment, just dropping the -rompath Thread 7 received signal SIGSEGV, Segmentation fault. [Switching to Thread 15116.0x2a18] 0x00007ffaf6a04521 in msvcrt!memmove () from C:\WINDOWS\System32\msvcrt.dll (gdb) bt 10 #0 0x00007ffaf6a04521 in msvcrt!memmove () from C:\WINDOWS\System32\msvcrt.dll #1 0x000000014b24bb6a in bgfx::d3d12::TextureD3D12::update(ID3D12GraphicsCommandList*, unsigned char, unsigned char, bgfx::Rect const&, unsigned short, unsigned short, unsigned short, bgfx::Memory const*) () #2 0x000000014add23d7 in bgfx::Context::flushTextureUpdateBatch(bgfx::CommandBuffer&) () #3 0x000000014addd7cf in bgfx::Context::renderThread(bx::Thread*, void*) () #4 0x00007ffaf5bf7034 in KERNEL32!BaseThreadInitThunk () from C:\WINDOWS\System32\kernel32.dll #5 0x00007ffaf6f22651 in ntdll!RtlUserThreadStart () from C:\WINDOWS\SYSTEM32\ntdll.dll #6 0x0000000000000000 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) |
 No.18570
Robbbert Senior Tester
Mar 16, 2021, 13:31
|
Confirmed crash. Happens while the screen is still black, before any text appears. The dump is basically nonsense, but seems to point to a bad memcpy. |
|
No.18688
Andrew Tester
Apr 13, 2021, 14:23
|
Same issue with gtfore06: E:\emulator-mame>mame.exe gtfore06 -norc -video bgfx -bgfx_backend d3d12 -rompath e:\arcade;e:\arcade-chd g4c-us-u.u53 NOT FOUND (NO GOOD DUMP KNOWN) (tried in gtfore06 iteagle) WARNING: the machine might not run correctly. ----------------------------------------------------- Exception at EIP=00007ffb98ac44d3 (__cxa_throw_bad_array_new_length+0x4c984253): ACCESS VIOLATION While attempting to write memory at 0000000034fd0000 ----------------------------------------------------- RAX=0000000034fcf800 RBX=0000000000000a80 RCX=0000000034fd0010 RDX=fffffffffa9668e0 RSI=00000000000fc000 RDI=00000000000bf800 RBP=000000000a23f9d0 RSP=000000000a23f9a8 R8=0000000000000030 R9=0000000000000009 R10=0000000029c37230 R11=000000002f936b60 R12=0000000000000180 R13=000000002f83ab50 R14=0000000000000a80 R15=0000000000000180 ----------------------------------------------------- Stack crawl: 000000000a23f9a0: 00007ffb98ac44d3 (memcpy+0x0113) 000000000a23f9d0: 000000014a68bfad (bx::memCopy(void*, void const*, unsigned long long)+0x000d) 000000000a23fbd0: 000000014aaf9e9a (bgfx::d3d12::TextureD3D12::update(ID3D12GraphicsCommandList*, unsigned char, unsigned char, bgfx::Rect const&, unsigned short, unsigned short, unsigned short, bgfx::Memory const*)+0x01fa) 000000000a23fc30: 000000014ab0951e (bgfx::d3d12::RendererContextD3D12::updateTexture(bgfx::TextureHandle, unsigned char, unsigned char, bgfx::Rect const&, unsigned short, unsigned short, unsigned short, bgfx::Memory const*)+0x005e) 000000000a23fd30: 000000014a6a4d24 (bgfx::Context::flushTextureUpdateBatch(bgfx::CommandBuffer&)+0x0234) 000000000a23fea0: 000000014a6a4e61 (bgfx::Context::rendererExecCommands(bgfx::CommandBuffer&)+0x00e1) 000000000a23fee0: 000000014a6b0007 (bgfx::Context::renderThread(bx::Thread*, void*)+0x00c7) 000000000a23ff20: 000000014aaca845 (bx::ThreadInternal::threadFunc(void*)+0x0035) 000000000a23ff50: 00007ffb9a017034 (BaseThreadInitThunk+0x0014) 000000000a23ffd0: 00007ffb9a722651 (RtlUserThreadStart+0x0021) |
|
No.20820
Firewave Senior Tester
Nov 15, 2022, 09:04
edited on: Dec 5, 2022, 20:06
|
I can still reproduce this with the official 0.249 Windows binary. I also tried all other BGFX backends and they are working fine. I am not able to reproduce this with any BGFX backend on Linux. But I wonder if this might have a similar cause as https://mametesters.org/view.php?id=8512 |