[Regression] After Burner Climax - Crashing on menu (#13875)

andylowemedia commented 1 year ago

Quick summary

Running After Burner Climax on RPCS3 on an Apple M1 MAX. It was working fine and then after an update it crashes at the menu screen.

Details

Running After Burner Climax on RPCS3 on an Apple M1 MAX. It was working fine and then after an update it crashes at the menu screen. I'm not aware of which build it was where it worked. This is the following output from the log console:

Log Output

- SYS: RPCS3 v0.0.28-15353-a828c214 Alpha | master
- SYS: VirtualApple @ 2.50GHz | 10 Threads | 64.00 GiB RAM | TSC: 1.000GHz
- SYS: Operating system: macOS, Version: 13.4.1
- SYS: Current Time: 2023-07-14T17:32:51
- RSX: Found vulkan-compatible GPU: 'Apple M1 Max' running on driver 0.2.988
- SYS: Firmware version: 4.90
S PPU: Enabled: Non-Java Mode Fixup
E PPU: Can't build instruction VSL
E PPU: Can't build instruction VSR
- RSX: Found vulkan-compatible GPU: 'Apple M1 Max' running on driver 0.2.988
E RSX: Your GPU driver does not support some required MSAA features. MSAA will be disabled.
E RSX: Your GPU does not support double precision floats in shaders. Graphics may not render correctly.
E RSX: Your GPU does not support depth bounds testing. Graphics may not render correctly.
E RSX: Your GPU does not support wide lines. Graphics may not render correctly.
E RSX: Your GPU does not support framebuffer logical operations. Graphics may not render correctly.
E RSX: Apple GPUs are incompatible with the current implementation of asynchronous texture decoding.
S HID: DualShock 4 Controllers found: 1
S Input: The pad mode was changed to Single-threaded
S Input: DualShock 4 device 0 connected
S GUI: Boot successful.
S PPU: LLVM: Loaded module v6-kusa-tGrUK85GgkjarnCtdio3Hi-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-SJosc8dabnwYWRyg4hzy6K-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-YACwz9mp0LKby91qqMqnJf-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-rR58yW7wntyEUaaRnNRX64-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-Mng8QYJ17JLYV0LKWxuCFF-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-RLfdnuv9X6PmvCJeSHSfUz-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-SRsedLsWygvYbsrNETuLfT-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-jQFk54Zki7Jco12kN7gGU2-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-Yq4vk1XAffxYFdCsChacVe-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-6GGVLWxuAUsakv9y3Pk6AW-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-dKJ4djccYM3GhcYUd7CaAh-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-Ezhz0zW5z8c7fq1i9wXs3j-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-qUgYjxtm4XJ8vqC0doWYwW-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-hTte0ixgNY8NwQ2jmspw1W-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-Q1UAGNaSzv1kRE9gHMTmW0-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-maK74F7CYYPEvQVks4eAQp-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-fPV0TkFaMMytfLExV0ZiX9-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-gC6jTYZhHMArf7405QWw9E-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-mFJJxHZVmuuFxjx2hCp0Ns-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-5N5bYWKN3s78qcu5whxQFd-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-dLQReLYrbAUjVZvCdXFTJj-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-8RJYPuo0KycY4V3xoC2sgb-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-FKGhd4HMnv6iAeSsxQvumV-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-AW1pKNRuyE95HXAH4QJHzd-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-AtVqtVGWVgUQqkG3wfdvrG-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-kLbQZHXsHZwtH1AtCYMdzf-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-7aewFgCL3gA2fQ8ag56LYL-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-cxxhk3cpswg4NzCM0ZAaqo-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-CZMuza8guboFv9s5dniPMv-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-TbfjiqeCNzcW8zU7wP6ZaJ-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-WuNpLPkxoEvFPeJv4bEUdz-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-A23rUvfFfeP0AN0tgohbd4-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-S1ijgrg54SzXvfSm91Ux4V-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-5AFNHSmA6wSVkqtbJuMcYV-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-h3ngGPYsxrpbikYe9Lzp8m-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-j6TvkM4mqV3HwG2GgTSkvL-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-JzeWEng62G75JsXVYp00mG-00001G-westmere.obj
S SPU: SPU Runtime: Built the interpreter.
S SPU: SPU Runtime: Built 1248 functions.
U sys_prx TODO: _sys_prx_register_module(name=“cellProcessElf”, opt=*0xd0058ce0)
S PPU: LLVM: Loaded module v6-kusa-1z3Pyu8YVnnorJiQ2hfu1e-00001G-westmere.obj
S sys_prx: Loaded module: “/dev_flash/sys/external/libsysmodule.sprx” (id=0x23000b00)
U sys_ss TODO: sys_ss_access_control_engine(pkg_id=0x1, a2=0x1, a3=0xd0058a50)
E SYS: 'sys_ss_access_control_engine' failed with 0x80010003 : CELL_ENOSYS [1]
U sys_ss TODO: sys_ss_access_control_engine(pkg_id=0x2, a2=0xd0058a50, a3=0x0)
S PPU: LLVM: Loaded module v6-kusa-XCgQWMc1s99n1WTwrpWvw4-00001G-westmere.obj
S sys_prx: Loaded module: “/dev_flash/sys/external/libgcm_sys.sprx” (id=0x23000e00)
S PPU: LLVM: Loaded module v6-kusa-1Au1tg93M0j9aPxhbpVJAC-00001G-westmere.obj
S PPU: LLVM: Loaded module v6-kusa-5MR5UPWcNoRKHsUNJqHbKV-00001G-westmere.obj
S sys_prx: Loaded module: “/dev_flash/sys/external/libsre.sprx” (id=0x23001100)
U sys_prx TODO: _sys_prx_register_module(name=“_sysProcessElf”, opt=*0xd0058df0)
S PPU: LLVM: Loaded module v6-kusa-ZAhea3FFhakpfMa36ZvaNx-00001G-westmere.obj
S sys_prx: Loaded module: “/dev_flash/sys/external/librtc.sprx” (id=0x23002f00)
S PPU: LLVM: Loaded module v6-kusa-fLV79QqHgPi90UziTsWrHo-00001G-westmere.obj
S sys_prx: Loaded module: “/dev_flash/sys/external/libfs.sprx” (id=0x23003000)
S PPU: LLVM: Loaded module v6-kusa-UnNP3fZh95wiCGy3Q0csRy-00001G-westmere.obj
S sys_prx: Loaded module: “/dev_flash/sys/external/libresc.sprx” (id=0x23004600)
U cellNetCtl TODO: cellNetCtlAddHandler(handler=*0x4d7088, arg=*0x0, hid=*0x14ff950)
E SYS: '_sys_lwmutex_lock' failed with 0x80010005 : CELL_ESRCH [1]
E SYS: '_sys_lwmutex_lock' failed with 0x80010005 : CELL_ESRCH [2]
E SYS: '_sys_lwmutex_lock' failed with 0x80010005 : CELL_ESRCH [3]
U sys_prx TODO: _sys_prx_get_module_id_by_name(name=“cellLibprof”, flags=0, pOpt=*0x0)
E sys_fs: 'sys_fs_stat' failed with 0x80010006 : CELL_ENOENT, “/dev_hdd0/game/NPEB00175/USRDIR/dev_hdd0/game/NPEB00175/USRDIR/rom/adx/voice.afs” [1]
E SYS: 'cellSaveDataFixedLoad2' failed with 0x8002b401 : CELL_SAVEDATA_ERROR_CBRESULT [1]
E SYS: 'cellMsgDialogAbort' failed with 0x8002b302 : CELL_MSGDIALOG_ERROR_DIALOG_NOT_OPENED [1]
E sys_fs: 'sys_fs_stat' failed with 0x80010006 : CELL_ENOENT, “/dev_hdd0/game/NPEB00175/USRDIR/dev_hdd0/game/NPEB00175/USRDIR/rom/adx/ABC_HIRO_LOOP.adx” [1]
E SYS: 'sys_ppu_thread_join' failed with 0x80010005 : CELL_ESRCH [1]
E SYS: 'sys_ppu_thread_join' failed with 0x80010005 : CELL_ESRCH [2]
E SYS: 'sys_ppu_thread_join' failed with 0x80010005 : CELL_ESRCH [3]
E RSX: Format incompatibility detected, reporting failure to force data copy (VK_FORMAT=0x7C, GCM_FORMAT=0x83)
F {RSX [0x05166b0]} SIG: Thread terminated due to fatal error: Verification failed
(in file /private/var/folders/76/zy5ktkns50v6gt5g8r0sf6sc0000gn/T/cirrus-ci-build/rpcs3/Emu/RSX/VK/VKTexture.cpp:64[:3], in function copy_image_to_buffer) (errno=316=Unknown error: 316)

Build with regression

v0.0.27-15033-e1744cea

Attach two log files

Error RPCS3.log Working RPCS3.log

Attach capture files for visual issues

No response

System configuration

No response

Other details

No response

Asinin3 commented 1 year ago

I don't think you have actually tested this for regressions properly. You state that the build with regression is 15033, but that PR was just a change to the debugging tools. Have you actually confirmed which build breaks it? Use https://rpcs3.net/compatibility?b&p=5 Go to old builds and narrow down exactly what build causes the issue.

Don't go one build at a time, go back months at a time until you find where it starts to work again. Then go in-between where it worked and broke until you narrow down exactly what build caused the issue.

andylowemedia commented 1 year ago

Thanks for the comment, I did this however there are many skipped Mac builds between 0.0.27-15005 and 0.0.27-15033 and the two in between, builds 0.0.27-15008 and 0.0.27-15015, wouldn't even load a game list. Now I can't load any of the other builds as my setup if is Mac only, and when it was noted that the logs were needed for in game and so I supplied the best I could there. I did make it clear that this error was only on the Mac M1 Max. However if this means that the regression can not be found as you need to identity which build it was in between the available Mac builds then I understand.

Asinin3 commented 1 year ago

If you've narrowed it down, thats good enough. "between 0.0.27-15008 and 0.0.27-15015," is good info. Before you only listed one build with nothing stating if t happened around that time, for all we knew it could've happened months prior.

If I had to make a guess, I would say its probably caused by https://github.com/RPCS3/rpcs3/pull/13875 . But it might be something else. Did you clear all caches etc when testing newer build?

kd-11 commented 1 year ago

https://github.com/RPCS3/rpcs3/pull/13875 added the checks to catch this type of error. Previously it would have silently sent the incorrect dimensions to the hardware and caused some random device lost errors on NVIDIA.

andylowemedia commented 1 year ago

If you've narrowed it down, thats good enough. "between 0.0.27-15008 and 0.0.27-15015," is good info. Before you only listed one build with nothing stating if t happened around that time, for all we knew it could've happened months prior.

If I had to make a guess, I would say its probably caused by #13875 . But it might be something else. Did you clear all caches etc when testing newer build?

Every time I try a new build, I always clear the caches. I even tend to that every time I update to the latest build as well.

kd-11 commented 1 year ago

I'm unable to reproduce any crashing. What are you doing in the menus to trigger the crash?

andylowemedia commented 1 year ago

Nothing, it just happens as soon as the start menu happens, sometimes I can press start sometimes not. It just crashes. Always with the same error that I posted. But its always after loading save data, I have even tried deleting the save data and it still happens.

andylowemedia commented 1 year ago

One thing I have noticed is that in the logs: " /private/var/folders/76/zy5ktkns50v6gt5g8r0sf6sc0000gn/T/cirrus-ci-build/rpcs3/Emu/RSX/VK/VKTexture.cpp" This file doesn't exist in my file system.

kd-11 commented 1 year ago

One thing I have noticed is that in the logs: " /private/var/folders/76/zy5ktkns50v6gt5g8r0sf6sc0000gn/T/cirrus-ci-build/rpcs3/Emu/RSX/VK/VKTexture.cpp" This file doesn't exist in my file system.

It just means it existed on the cloud machine that compiled your build.

Asinin3 commented 1 year ago

Working here on Windows atleast.

Satan86 commented 1 year ago

Should be fixed by #14446

andylowemedia commented 1 year ago

Still doesn't work with the exact same error at the exact same time, as of testing build 0.0.29-15476. I had cleared all of the caches in the menu.

andylowemedia commented 5 months ago

Any progress with this?

RPCS3 / rpcs3