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

GPD XD: PPSSPP crashing when switching apps #11063

Closed
tiagaoextremo opened this issue May 22, 2018 · 35 comments
Closed

GPD XD: PPSSPP crashing when switching apps #11063

tiagaoextremo opened this issue May 22, 2018 · 35 comments
Milestone

Comments

@tiagaoextremo
Copy link

What happens?

Usually when playing some rpgs i would check from time to time a walkthrough in .txt format switching between the txt reader and the ppsspp emulator. For the latest versions the emulator is crashing everytime i would switch to another app, even if i press the home button the emulator crashes when i return to it.

What should happen?

It should be able to switch between the ppsspp emulator and any other apps.

What hardware, operating system, and PPSSPP version? On desktop, GPU matters for graphical issues.

GPD XD, RK3288, Mali T760, Android Kitkat 4.4.4, nightly build version v1.5.4-993-gab65c5210.

@tiagaoextremo
Copy link
Author

Should i provide some kind of logcat?

@hrydgard
Copy link
Owner

If you can, please do.

@tiagaoextremo
Copy link
Author

Sorry about the noob question, but how should i proceed in order to do it?

@ChurroBoi
Copy link

I experience this as well. I can get a log if you need?

@tiagaoextremo
Copy link
Author

@ChurroBoi I would appreciate that, if you don't mind.

@ChurroBoi
Copy link

@hrydgard
Copy link
Owner

Thanks. It's very likely to be dying in or close to GLQueueRunner::RunInitSteps and it looks similar to previous GPD stack traces where it blew up on minor GL errors.. Need to get it error-clean.

@tiagaoextremo
Copy link
Author

Thanks @ChurroBoi for posting the log and thanks @hrydgard for looking into it.

@03bgood
Copy link

03bgood commented Jun 1, 2018

Yeah, this keeps happening to me as well. If I hit the home button and then return to the app, it either freezes up on me or I get a black screen (which is fixed by going into settings) is the developer aware of this situation? I didn't notice this until now. Even reinstalling it didn't help nor resetting to default settings.

@tiagaoextremo
Copy link
Author

I just tried latest version (v1.6.2-4-g30de8194a), still the same. Fingers crossed that this will be fixed.

@tiagaoextremo
Copy link
Author

Hi @hrydgard i'm asking this just for curiosity. This issue happening with the GPD XD it's some thing that could be fixed someday or it's more complicated than it seems? I'm still trying once a week the nightly builds, but it's the same crashing. Thanks.

@hrydgard
Copy link
Owner

hrydgard commented Oct 3, 2018

Right, I do plan to fix this...

@hrydgard hrydgard added this to the v1.7.0 milestone Oct 3, 2018
hrydgard added a commit that referenced this issue Oct 6, 2018
…1063

The context is already lost and we're really running shutdown when the process is woken
up again. Additionally, orderly shutdown through the button doesn't happen
on the render thread so remove a couple of asserts that are wrong.
hrydgard added a commit that referenced this issue Oct 6, 2018
…1063

The context is already lost and we're really running shutdown when the process is woken
up again. Additionally, orderly shutdown through the button doesn't happen
on the render thread so remove a couple of asserts that are wrong.
unknownbrackets added a commit that referenced this issue Oct 6, 2018
Avoid calling any GL calls during shutdown on Android. Should help #11063
@hrydgard
Copy link
Owner

hrydgard commented Oct 6, 2018

Can you try this again with the latest build?

@tiagaoextremo
Copy link
Author

tiagaoextremo commented Oct 6, 2018

Hi Henrik. I just tried the build v1.6.3-547-g8a74e6f7b. Still crashing. I also tried the v1.6.3-548-geba6c00a8 and the same results, whether it's the home button or i exchange to another app still crashes the emulator. Thanks for looking into it.

@hrydgard
Copy link
Owner

hrydgard commented Oct 7, 2018

Thanks for testing @tiagaoextremo . Sorry it didn't help, I'm running out of ideas on how to fix it...

Think you could get some fresh ADB logs?

@tiagaoextremo
Copy link
Author

ppsspp_crashing_gpd_xd.txt

I hope it worked. I didn't knew how to get a ADB log, but i looked into google and i'm assuming it's ok. After setting everything i just turned on the device, opened PPSSPP and after loading a game i pressed the home button, which made the emulator crashed. This is the log generated after that. Thanks again.

@unknownbrackets
Copy link
Collaborator

You can see instructions here:
https://github.com/hrydgard/ppsspp/wiki/How-to-get-an-adb-logcat-from-a-PC

It looks like some of the log information wasn't captured in that log above.

-[Unknown]

@hrydgard
Copy link
Owner

hrydgard commented Oct 7, 2018

Yeah that's missing the crash itself. @tiagaoextremo btw does it make a difference whether you set Display Resolution to native or 2x or something?

@tiagaoextremo
Copy link
Author

ppsspp.log

Thanks @unknownbrackets. I followed your instructions. Is it correct now?

@hrydgard I just noticed that PPSSPP crashes when i select any other option besides "2X PSP", the other options Native, Auto or 1X crashes the emulator. Rendering resolution allows me to change with no issues.

@hrydgard
Copy link
Owner

hrydgard commented Oct 7, 2018

Right ok, it'll be defaulting to 2X I guess and then any change will crash.

@unknownbrackets
Copy link
Collaborator

Thanks, this is a good log.

I/WindowState(  486): WIN DEATH: Window{42d20918 u0 org.ppsspp.ppsspp/org.ppsspp.ppsspp.PpssppActivity}
W/ActivityManager(  486): Exception thrown during pause
W/ActivityManager(  486): android.os.DeadObjectException
W/ActivityManager(  486): 	at android.os.BinderProxy.transact(Native Method)
W/ActivityManager(  486): 	at android.app.ApplicationThreadProxy.schedulePauseActivity(ApplicationThreadNative.java:660)

Hm, that's interesting? Anyway, seems you restarted it, and then:

I/PPSSPP  ( 3101): GPU_GLES: DeviceLost
I/PPSSPP  ( 3101): NativeShutdownGraphics
I/PPSSPP  ( 3101): NativeShutdownGraphics done
I/PPSSPP  ( 3101): GL submission thread paused. Frame=0
I/PPSSPP  ( 3101): Leaving emu thread
I/PPSSPP  ( 3101): EmuThreadJoin - joined
I/PPSSPP  ( 3101): ThreadEnd
D/MaliGPU ( 3101): GPU DDK VERSION: [r4p1-00rel0-11-8@0]
F/libc    ( 3101): Fatal signal 11 (SIGSEGV) at 0x0000001f (code=1), thread 3116 (AndroidRender)
I/DEBUG   (  144): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG   (  144): Build fingerprint: 'google/hammerhead/hammerhead/4.4.4/KTU84Q/eng.skelton.20150927.102903:eng/test-keys'
I/DEBUG   (  144): Revision: '0'
I/DEBUG   (  144): pid: 3101, tid: 3116, name: AndroidRender  >>> org.ppsspp.ppsspp <<<
I/DEBUG   (  144): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000001f
I/DEBUG   (  144): backtrace:
I/DEBUG   (  144):     #00  pc 00a58b20  /data/app-lib/org.ppsspp.ppsspp-1/libppsspp_jni.so
I/DEBUG   (  144):     #01  pc 00a58943  /data/app-lib/org.ppsspp.ppsspp-1/libppsspp_jni.so
I/DEBUG   (  144):     #02  pc 00a426f3  /data/app-lib/org.ppsspp.ppsspp-1/libppsspp_jni.so (__gxx_personality_v0+330)
I/DEBUG   (  144):     #03  pc 0003c570  /system/lib/libc.so (__gnu_Unwind_Backtrace+152)
I/DEBUG   (  144):     #04  pc 0003ca90  /system/lib/libc.so (___Unwind_Backtrace+20)
...
I/DEBUG   (  144):          789bb508  773299d9  /data/app-lib/org.ppsspp.ppsspp-1/libppsspp_jni.so (GLRShader::~GLRShader()+12)

So seems like we're still killing a GLRShader during restore?

-[Unknown]

@hrydgard
Copy link
Owner

hrydgard commented Oct 11, 2018

Indeed so, will look into that. Although a cursory code review did not reveal anything, I think I'll have to debug this on device.

@hrydgard
Copy link
Owner

OK, checked in another potential fix... let's hope it's enough this time.

@tiagaoextremo
Copy link
Author

Hi Henrik, i just tried this build. Still the same crashing. Would you like a fresh log or is there any other way a noob like me could help?

@hrydgard
Copy link
Owner

Yes please, without a device, logs are the most useful way we have...

@tiagaoextremo
Copy link
Author

ppsspp.log

Here goes. Hope it helps. :)

@unknownbrackets
Copy link
Collaborator

Darn, still a GLRShader destructor in the stack...

-[Unknown]

@hrydgard
Copy link
Owner

Alright, can you give it another go @tiagaoextremo ? Thanks!

@tiagaoextremo
Copy link
Author

ppsspp.log

Hi Henrik, i tried version 1.6.3-576-g292d2f44e. I'm sorry to say that it crashed again, log included. Sorry that this issue is giving you guys so much trouble. Lately i've been using a lot the save states just in case that this is something that can't be fixed. Thanks for all your work with this emulator, it's one of the best!

@hrydgard
Copy link
Owner

Oh duh, I see what I missed. Don't worry about it, thank you for all your testing, you'll have to test one more I'm afraid :)

@hrydgard
Copy link
Owner

Github clearly has some problems, it's sometimes showing me old versions of this thread so sorry for any double posts. But I've committed a yet another fix :) Please give it a try. Really want to get this done before the release...

hrydgard pushed a commit that referenced this issue Oct 22, 2018
@tiagaoextremo
Copy link
Author

Hi, Henrik. First let me say thanks again. It's been finally fixed! Now i can play a few rpgs again checking some faqs and the emulator isn't crashing anymore. Also, now i can change the resolution to 1x or 2x, isn't crashing also. Your work is highly appreciated! Also thanks to @unknownbrackets for tips and helping me to create a proper log.

@unknownbrackets
Copy link
Collaborator

Hurray - thanks for validating, glad to hear it's fixed.

-[Unknown]

@hrydgard
Copy link
Owner

Oh awesome! Thanks yet again for all your testing!

@ghost
Copy link

ghost commented Apr 21, 2020

Look like this issue has revive see #12843

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

No branches or pull requests

5 participants