| カテゴリ | 重要度 | ステータス | 解決状況 | 登録日時 | 最終更新 |
|---|---|---|---|---|---|
 クラッシュ/フリーズ | 重要 (本体) | 認証済み | 未処理 | 2025-12-10 07:55 | 2025-12-11 18:52 |
| テスター | john_iv | 担当者 | ソース | ||
| バージョン | 0.283 | 発生バージョン | 修正バージョン | ||
| 修正コミット | プルリク | ||||
| フラグ | |||||
| セット | All | ||||
| セット詳細 | |||||
| 概 要 | -numscreens 2 オプションがクラッシュする。 | ||||
| 詳 細 | This has been a longstanding bug on my system going back at least three years; through official releases and builds from tip of tree. Launching 'mame dkong -norc -numscreens 2 -video bgfx' produces a crash as it tries to start its full screen instances. I get one screen showing briefly (1 second) on monitor 2 before it crashes out. It crashes regardless if -screen is set to auto or mapped to \\.\DISPLAY1, 2 etc. for screen0 and/or screen1. Note: It *works successfully* if I launch in windowed mode and then alt-enter to take them both fullscreen. 'mame dkong -norc -numscreens2 -window'. The fullscreen fails as well with -video d3d and DirectX9 runtimes. c:\O\Games\MAME>mt dkong -numscreens 2 -nowindow -video d3d Unable to create the Direct3D device (8876086C) Unable to initialize Direct3D 9 Fatal error: Unable to complete window creation ----------------------------------------------------- Exception at EIP=00007ff63915ae96 (not found): ACCESS VIOLATION While attempting to read memory at 0000016a99261cc0 ----------------------------------------------------- RAX=0000016a99261c90 RBX=000000000000001c RCX=0000016a96f40c00 RDX=00000000ffffffeb RSI=0000016a99261c90 RDI=0000000000040a4c RBP=0000000000000000 RSP=00000028c40f91a0 R8=0000000000000000 R9=0000000000002658 R10=0000000000040a4c R11=0000000000000246 R12=0000000000000000 R13=0000000000000000 R14=0000000080009011 R15=0000000000000000 ----------------------------------------------------- Stack crawl: 00000028c40f9290: 00007ff63915ae96 (not found) 00000028c40f93f0: 00007fff48be7846 (CallWindowProcW+0x06a6) 00000028c40f9450: 00007fff48be70cc (SendMessageW+0x0acc) 00000028c40f94b0: 00007fff48c17e93 (GetWindowDpiAwarenessContext+0x01f3) 00000028c40f9538: 00007fff49fe5be4 (KiUserCallbackDispatcher+0x0024) 00000028c40f9540: 00007fff47122544 (NtUserDestroyWindow+0x0014) 00000028c40f9570: 00007ff639bc3cbe (not found) 00000028c40f95b0: 00007ff639155c29 (not found) 00000028c40f95e0: 00007ff638ea39d0 (not found) 00000028c40f9760: 00007ff63905167a (not found) 00000028c40fed70: 00007ff639137700 (not found) 00000028c40ff150: 00007ff639a94586 (not found) 00000028c40ff450: 00007ff639a94b38 (not found) 00000028c40ff4b0: 00007ff639132666 (not found) 00000028c40ff870: 00007ff63b6dbd07 (luaopen_lfs+0xafc157) 00000028c40ff910: 00007ff638e910c9 (not found) 00000028c40ff940: 00007ff638e91416 (not found) 00000028c40ff970: 00007fff4879e8d7 (BaseThreadInitThunk+0x0017) 00000028c40ff9c0: 00007fff49f0c53c (RtlUserThreadStart+0x002c) I am unclear if this is just a 'my system' error as I only have one setup w/ multiple monitors to test this against and have had only one video card over the last few years. The crash in Mame has happened through multiple GPU driver iterations. | ||||
| 再現手順 | 1. Two physical monitors connected to a video card. 2. Use the following command line, using -norc to take any config oddities out of the mix: mame.exe dkong -numscreens 2 -norc -video bgfx Crash from tiny build (dkong.cpp) symbols level 2. ----------------------------------------------------- Exception at EIP=00007ff63b47cc38 (not found): ACCESS VIOLATION While attempting to read memory at 00007ff233affe40 ----------------------------------------------------- RAX=fffffffbf8000000 RBX=000001fa9de74308 RCX=0000000000000000 RDX=00007ff63baffe40 RSI=000000000000fd20 RDI=0000000b6b5727cc RBP=0000000000000000 RSP=000000c8afbff530 R8=0000000000000000 R9=0101010101010101 R10=0000000000000000 R11=000000c8afbff380 R12=000001fa9f548040 R13=0000000000000000 R14=0000000000000000 R15=0000000000000000 ----------------------------------------------------- Stack crawl: 000000c8afbff5e0: 00007ff63b47cc38 (luaopen_lfs+0x89d088) 000000c8afbffc20: 00007ff63b46dc9c (luaopen_lfs+0x88e0ec) 000000c8afbffc80: 00007ff63b158df3 (luaopen_lfs+0x579243) 000000c8afbffcc0: 00007ff63b162646 (luaopen_lfs+0x582a96) 000000c8afbffcf0: 00007fff4879e8d7 (BaseThreadInitThunk+0x0017) 000000c8afbffd40: 00007fff49f0c53c (RtlUserThreadStart+0x002c) | ||||
| 追加情報 | ==== System Summary ==== OS : Microsoft Windows 11 Pro (v10.0.26200, 64-bit) CPU : 12th Gen Intel(R) Core(TM) i7-12700K @ 3600MHz (12 cores/20 threads) RAM : 64 GB (5200) BIOS : American Megatrends Inc. v4301 (Released: 04/28/2025) Motherboard : ASUSTeK COMPUTER INC. ROG STRIX Z690-F GAMING WIFI (SN: 210890277200824) GPU : AMD Radeon RX 5600 XT - 5.96 GB (Driver: 32.0.21033.3005) Adapters : Intel(R) Ethernet Controller (3) I225-V – IP: 192.168.1.3, fe80::2792:22b6:2447:a603 – MAC: 04:42:1A:2C:12:2C – GW: 192.168.1.1 | ||||
| 添付ファイル | |||||