kd-11
kd-11
I think that makes sense if the desktop is accelerated using the nvidia card but rpcs3 is rendering on AMD since the data has to be copied over.
Could just be ASLR (https://github.com/RPCS3/rpcs3/pull/16878) I'll have to find time in the next few weeks to look at this.
Hopefully other generations of mac are affected, I'm not likely to purchase an M4 any time soon (I'm still on M1)
This is trivial to fix, so tagging myself so I don't forget.
Settings -> Emulator -> LLVM compiler threads Choose a value less than your CPU core count.
> Went down to 31 but did not help.. [RPCS3.log](https://github.com/user-attachments/files/18464074/RPCS3.log) I was thinking more like start with a handful and figure out your safe limit. Going down 1 or 2...
We cannot detect defective hardware when the defect kills the app. This would require collaboration with intel and motherboard vendors to tell us that a cpu may have already degraded....
One thing to note: If vmin shift already caused internal damage then bios can never truly fix it. It will still crash. The bios update just prevents further damage from...
> I changed some codes in RSXThread.cpp, it seems can fix this problem. idk whether it'll cause other issue. [@elad335](https://github.com/elad335) [@digant73](https://github.com/digant73) This is wrong, continue is the right action there....
It's still wrong. You can also just disable the function and it wont crash. Restart indices are a normal part of graphics rendering. first + count is generating a value...