Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PPSSPPDebug.exe freezing on closing #4803

Closed
ghost opened this issue Dec 12, 2013 · 11 comments
Closed

PPSSPPDebug.exe freezing on closing #4803

ghost opened this issue Dec 12, 2013 · 11 comments

Comments

@ghost
Copy link

ghost commented Dec 12, 2013

I've to tell you some details about this debug build, I had to turn off the incremental linking because it was causing errors, also I had DirectX SDK (June 2010) already installed so I changed the SDK shortcut folder, to use my files instead of the submodule, though I don't know if this affected the compiled files in any way.

Now about this test, I didn't run a debug build for a lot of time because VC++ 2010 Express was causing conflicts with multiple versions of cvtres.exe and I didn't know it (found the cause just today, thanks to this answer), I can run debugs once again.

This first test was smooth (tried to play Sword Art Online), the game didn't cause any kind of problem and after playing for awhile it exited correctly (back to ppsspp main menu), then I tried to close the emu simply clicking "Exit" and that is when it freezed, VC++ 2010 Express reported:

Unhandled exception at 0x77238e19 (ntdll.dll) in PPSSPPDebug.exe: 0xC0000005: Access violation writing location 0x00000014

It didn't save the log but, I could save the stack trace:
http://pastebin.com/F5cexPMM

Variables:
http://imgur.com/a/dwXUH#0

Debug Output:
http://pastebin.com/KJ3eb6Ym

Everything above:
https://mega.co.nz/#F!kp8SkKyC!Rui5T3Ri46Z9vmhMFWtw-Q

This debug build was run using latest commit files (0bfe9db9ab), including latest submodules (except directx).

@unknownbrackets
Copy link
Collaborator

It must be something to do with another thread, I think. Is this with "multithreaded" on or off?

-[Unknown]

@hrydgard
Copy link
Owner

I see that one sometimes when exiting, but only in Debug mode and only when under the debugger so I've been too lazy to figure it out.

@bollu
Copy link
Contributor

bollu commented Dec 12, 2013

Yep, I have the exact same problem...

@ghost
Copy link
Author

ghost commented Dec 14, 2013

@unknownbrackets Runtime Library was set on "Multi-threaded Debug DLL (/MDd)" in all project files.

I'll try again using the incremental linking this time (it might work, since the problem was related to that exe) and the directx submodule that you provided here (actually, I didn't notice it before so that's why I used my SDK shortcut for this build, I noticed that submodule only while I was writing this issue.. xD), maybe it works better.

I forgot to mention that it was ignoring irregular read/writres during that build, maybe I should try again with SAO (I'll surely try to debug Kirameki once again, that game is so cursed...)


Edit: @unknownbrackets Runtime Library was set on "Multi-threaded Debug DLL (/MDd)" in all project files or did you mean PPSSPP Emulation settings? I didn't use Multithreaded in Emulation settings for that test.

@unknownbrackets
Copy link
Collaborator

I meant the PPSSPP settings, yeah.

Must be something in the debugger, then, taking too long to shut down.

-[Unknown]

@ghost
Copy link
Author

ghost commented Dec 14, 2013

Right now I'm running another debug, for Kirameki, and it reported an error in VC++ while I was playing but I cannot find a way to save the full debug console log of PPSSPP, the console didn't freeze this time, I can select and copy the last 9999 lines (that's the limit I set in the window settings) but the PPSSPPDebug.exe window froze and it won't let me click the "Debug" dropdown menu, to save a complete log.

Is there any way to force the log generation, in these situations? (or maybe is there any file in windows temp directories, where the lines prior to the last 9999 are being cached?). For now I'll save the stack trace like I did before and everything else that I can manage to save form this session, will post everything in Kirameki issue.

@unknownbrackets
Copy link
Collaborator

No, anything beyond the last 9999 lines is gone, unless you start it with --log=mylogfile.txt.

-[Unknown]

@unknownbrackets
Copy link
Collaborator

I don't remember if I ever hit this or not. I think I fixed something a while back. Maybe.

Does this still happen?

-[Unknown]

@thedax
Copy link
Collaborator

thedax commented Jan 30, 2014

I still periodically receive crashes when exiting the debug version; it's controller related iirc. I'll see if I can reproduce..

@unknownbrackets
Copy link
Collaborator

I still have not seen this in a while, any idea how to reproduce?

-[Unknown]

@unknownbrackets
Copy link
Collaborator

With a bunch of recent changes and #6586, I haven't really reproduced any debug crashes lately. I think I'll close this, but if there are steps to reproduce or any more information, and it's still happening, please comment/reopen.

-[Unknown]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants