Closed solarmystic closed 10 years ago
Interesting. Adding back the return fixes a BREAK and invalid memory access. Hmm. I wonder what the right thing is.
-[Unknown]
This doesn't seem to be happening anymore on newer 0.9.5 builds, unless it's an ATI only thing.
Yup it still happen if i tick both multithread and fastmemory and this happen on God Eater 2 too.
IIRC your laptop has an ATI/AMD GPU, right? So I guess that explains why I'm not seeing the crash.
Yup you're right :D
Actually, I've just retested this again using the latest 64bit build from Orphis, v0.9.5-916-gf3a0193, and I can't reproduce this crash anymore; I can enable both FastMem and MT together now in Gods Eater Burst (the first game) without any crashes.
But it seems like @Ritori's still getting it, so I assume that the issue must still exist in some form.
@Ritori, can you retest Gods Eater Burst (the first game) again? Just to be sure.
AMD crashes but Nvidia not ? I'll test it out as well tonight.
@solarmystic yup it still happen for me, i download latest 64bit version v0.9.5-925-g6277a95. Edit: ohh wait after i delete my old ppsspp.ini and start the game with both multithread and fast memory crash don't happen :D I think this can be close now.
Hmm, I wonder if some other setting impacts it?
-[Unknown]
@Ritori
Thanks for the report, I'll be closing this then.
@unknownbrackets about other setting you said... I try to experiment some setting again and it crash.
The setting that crash this Game :- Fast Memory, Multithread, Timer hack, Texture coord speedhack all on = Crash
if one these setting off crash don't occur :) Someone can confirm it?
Timer hack is extremely dangerous and I think we should probably hide it.
Okay i try experiment more setting look liked crash don't occur if i Off Prevent FPS from exceeding 60 with above post setting On. Edit :- I try experiment some other setting again look liked it randomly crash with randomly setting On and Off..
Frankly, I'm not quite sure whether this is a legitimate issue, since both options mentioned in the title are experimental/unstable and still not quite ready for primetime yet; i.e. not options you'd recommend users enable across the board for all games.
To reiterate, enabling both Fast Memory (FastMem) and Multithreaded (MT) simultaneously will crash the game and the emulator after booting with a 100% success rate.
Git bisect traced the issue back to this commit v0.9.1-116-g4d9eb24 https://github.com/hrydgard/ppsspp/commit/4d9eb24f29ec85966c881a73f553221e946466cb which was merged into master from v0.9.1-120-g3d0ad08 https://github.com/hrydgard/ppsspp/commit/3d0ad08dd2f0ffb7b84b25a2feb2848695c88e91 onwards
Last unaffected revision is the one right before the commit got merged into master, v0.9.1-118-g99c1ab3 https://github.com/hrydgard/ppsspp/commit/99c1ab38d7cee56c1edd3900fcb4eeece5b50e4c
Problem reproduction:-
Stack trace from an affected debug build using MSVC 2010 (only Disassembly available):-
Note:- It broke at the exact same point in both the release and debug builds' stacktrace.
Logfile from the first affected debug build until it crashes:- https://gist.github.com/solarmystic/6508692
Since the stack trace pointed to the Disassembly, it meant that the crash was most likely happening in JIT, so I disabled Dynarec (JIT) and tried to reproduce the issue again with both MT and FastMem enabled. Interestingly enough, the game did not crash in Interpreter Mode.
Caveats:-
Temporary solutions:-
Tested on a Core 2 Duo T9550 @ 2.8GHz, ATI Mobility Radeon 4670 and Windows 7 SP1 x64 machine.