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

[Android] Spider-Man 3 crashes unexpectedly #10196

Closed
Leopard20 opened this issue Nov 27, 2017 · 93 comments
Closed

[Android] Spider-Man 3 crashes unexpectedly #10196

Leopard20 opened this issue Nov 27, 2017 · 93 comments

Comments

@Leopard20
Copy link
Contributor

Leopard20 commented Nov 27, 2017

PPSSPP crashes in the first few seconds of the game. Don't know why or exactly when.

(So that search for the alternate spelling works: Spiderman 3).

@unknownbrackets
Copy link
Collaborator

Did this used to work in 1.4.2? Does it matter which GPU backend you use? What device? Do other games work?

Since you didn't provide any detail, we can't tell if you're using some obscure MIPS Warrior CPU or what.

Nothing can be done if you don't provide detail.

-[Unknown]

@Leopard20
Copy link
Contributor Author

Leopard20 commented Dec 1, 2017

I don't have access to the game right now, so I can't test on v1.4.2.
But I remember that the issue occurred on both backends.
I didn't notice crashes in other games like this (this game cashed when I was playing a level without skipping any videos or using load state) but I did notice crashes in Splinter Cell Essentials on load state and Field Commander when I skipped videos.

My GPU: Adreno 530 (Snapdragon 821 chipset)
I think the PPSSPP version was 1.4.2-894 or something.
I'll download the game later and let you know if I find anything new.

@Leopard20
Copy link
Contributor Author

Leopard20 commented Dec 4, 2017

Update: No crashes on the PC version. I only tested the OpenGL backend.

@unknownbrackets
Copy link
Collaborator

A few things that cause crashes have been fixed - does this still happen on the latest git build?

It'd be great to find the first build it stopped working on. For example, if you knew that 1.4.2 worked, you could test somewhere around v1.4.2-475-ged602a331. If that worked, try a newer build, if not, try an older. In 8 - 10 tests you could narrow down the change that caused it. Usually this makes it a lot easier to fix the issue.

If no previous version worked, it can be tricky.

-[Unknown]

@Leopard20 Leopard20 changed the title (Android) Spiderman 3 crash (Android) Spiderman 3 crashes unexpectedly Dec 4, 2017
@Leopard20
Copy link
Contributor Author

Leopard20 commented Dec 11, 2017

@unknownbrackets
I testesd some random builds since v1.4.2. Versions that had experimental tag for vulkan backend (such as 1.4.2-6) couldn't even run the game and crashed instantly. I didn't notice any difference between other builds. (including the most recent, 1.5.4-93)
This may have been random, but I noticed enabling the speed up tricks (lazy texture caching, disabling slower effects, etc) caused the game to crash faster. Without these options I could play all the way to the point where an explosion creates a hole in the wall (before it crashed when the second bunch of thugs entered the room). But as soon as I try to move through the hole the game crashes again.
I think it's because of graphical overload or something.

@Leopard20
Copy link
Contributor Author

Leopard20 commented Jun 5, 2018

This log was posted by @weihuoya in the above thread:
Spider-Man 3 only crash on android(JIT, IR, Interperter, and turning off fast memory)

    --------- beginning of crash
06-05 15:56:34.996 23936-23958/? A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x2300014000 in tid 23958 (Emu)
06-05 15:56:35.091 24481-24481/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-05 15:56:35.093 24481-24481/? A/DEBUG: Build fingerprint: 'samsung/hero2qltezc/hero2qltechn:7.0/NRD90M/G9350ZCU2BRD1:user/release-keys'
    Revision: '14'
    ABI: 'arm64'
06-05 15:56:35.094 24481-24481/? A/DEBUG: pid: 23936, tid: 23958, name: Emu  >>> org.ppsspp.ppsspp <<<
    signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x2300014000
06-05 15:56:35.095 24481-24481/? A/DEBUG:     x0   0000007f6ccbe0f4  x1   0000000000013ffe  x2   0000007f6f19eed6  x3   000000000000005d
        x4   0000007f6f19ef7c  x5   000000000000fffe  x6   000000000000fffe  x7   0000000008a14ef0
        x8   0000002300000000  x9   0000000004000000  x10  00000000000078cc  x11  0000000000000000
        x12  0000000000000003  x13  0000000000000000  x14  0000007f6eaabc60  x15  0000000000000000
        x16  0000007f6f647a88  x17  0000007f6eab7ef8  x18  0000000000000001  x19  0000007f6ccbe0f4
        x20  0000000000013ffe  x21  0000007f6f678f30  x22  0000000000000000  x23  0000007f6f6562a8
06-05 15:56:35.096 24481-24481/? A/DEBUG:     x24  0000007f6f6c0e94  x25  0000007f6f695708  x26  afb12da5406b7b53  x27  000000000000004b
        x28  0000007f6f656000  x29  0000007f6ccbe0e0  x30  0000007f6eab7ed0
        sp   0000007f6ccbe0c0  pc   0000007f6eab7f80  pstate 0000000060000000
06-05 15:56:35.136 24481-24481/? A/DEBUG: backtrace:
        #00 pc 0000000000450f80  /data/app/org.ppsspp.ppsspp-1/lib/arm64/libppsspp_jni.so (_ZN6Memory16ReadFromHardwareIjEEvRT_j+136)
        #01 pc 0000000000450ecc  /data/app/org.ppsspp.ppsspp-1/lib/arm64/libppsspp_jni.so (_ZN6Memory8Read_U32Ej+44)
        #02 pc 000000000044d348  /data/app/org.ppsspp.ppsspp-1/lib/arm64/libppsspp_jni.so (_Z22MIPSInterpret_RunUntily+88)
        #03 pc 0000000000464398  /data/app/org.ppsspp.ppsspp-1/lib/arm64/libppsspp_jni.so (_Z14PSP_RunLoopFori+84)
        #04 pc 0000000000565c18  /data/app/org.ppsspp.ppsspp-1/lib/arm64/libppsspp_jni.so (_ZN9EmuScreen6renderEv+336)
        #05 pc 000000000061c0fc  /data/app/org.ppsspp.ppsspp-1/lib/arm64/libppsspp_jni.so (_ZN13ScreenManager6renderEv+136)
06-05 15:56:35.137 24481-24481/? A/DEBUG:     #06 pc 000000000055dc3c  /data/app/org.ppsspp.ppsspp-1/lib/arm64/libppsspp_jni.so (_Z12NativeRenderP15GraphicsContext+644)
        #07 pc 00000000005584fc  /data/app/org.ppsspp.ppsspp-1/lib/arm64/libppsspp_jni.so (_Z20UpdateRunLoopAndroidP7_JNIEnv+44)
        #08 pc 0000000000559c58  /data/app/org.ppsspp.ppsspp-1/lib/arm64/libppsspp_jni.so
        #09 pc 00000000003a16f0  /data/app/org.ppsspp.ppsspp-1/lib/arm64/libppsspp_jni.so (_ZNSt6__ndk114__thread_proxyINS_5tupleIJNS_10unique_ptrINS_15__thread_structENS_14default_deleteIS3_EEEEPFvvEEEEEEPvSA_+44)
        #10 pc 000000000006885c  /system/lib64/libc.so (_ZL15__pthread_startPv+196)
        #11 pc 000000000001e118  /system/lib64/libc.so (__start_thread+16)

@Leopard20 Leopard20 changed the title (Android) Spiderman 3 crashes unexpectedly [Android] Spider-Man 3 crashes unexpectedly Jun 5, 2018
@unknownbrackets
Copy link
Collaborator

It's very strange that this crashes even in the interpreter, but only on Android. Just not sure what would be different between Android and Windows that would affect CPU emulation.

To confirm, PC is fine even in interpreter and with fast memory enabled?

-[Unknown]

@weihuoya
Copy link
Contributor

weihuoya commented Sep 3, 2018

PC run interpreter with fast memory enabled or disabled, both assert this message.
b3f86746-fd7a-4316-a288-78459453c6f8

		case 62: //sv.q
			if (addr & 0xF)
			{
				_dbg_assert_msg_(CPU, 0, "Misaligned sv.q");
			}

@unknownbrackets
Copy link
Collaborator

Oh, that's interesting. We definitely might not be handling misaligned sv.q the same in all jit backends...

-[Unknown]

@unknownbrackets
Copy link
Collaborator

Well, looking at the error more carefully - the fault is at 0x2300014000 right outside the scratchpad. So I guess it's not alignment...

Anyway, the behavior DOES differ a bit per backend:

  • Interpreter: copied without alignment (at 1 byte)
  • IR interpreter: stored as float * or on x86 potentially SSE aligned (may crash.)
  • x86: potentially MOVAPS in fast memory but not always, otherwise unaligned.
  • armv7: either 128 bit or 32 bit aligned, otherwise might crash.
  • arm64: probably unaligned.

Though, I guess that's not related after all.

-[Unknown]

@ghost
Copy link

ghost commented Oct 8, 2018

Game still crahes in the latest git build :(

@hrydgard hrydgard added this to the v1.9.0 milestone Feb 18, 2019
@ghost
Copy link

ghost commented Jul 8, 2019

Game still crashing Im using ppsspp v1.8.0-403 gbdd9d40a1
This is the part where the game always crashing 🤔
Screenshot_2019-07-08-16-25-58
GE Dump for Spider-Man 3 (Europe)
ULES00938_0001.ppdmp.zip

@ghost
Copy link

ghost commented Jul 8, 2019

This game doesn't crash in ppsspp v0.9.8 https://youtu.be/_L73ZLVJEHA and also it's performing better in my phone compare to the last gitbuild 🤔
I still didn't test v1.0 - v1.4 🤷
Screenshot_2019-07-08-23-18-19
Screenshot_2019-07-08-23-26-21
But have a bug in FPS it's lock in 30/30 not 60/60😅

@ghost
Copy link

ghost commented Jul 9, 2019

@unknownbrackets after several testing Spider-Man 3 didn't crash in v0.9.8 (performance better in my phone) and v0.9.9.1 (slow on my device with graphical glitches)

The game crash in area where I mentioned above tested in v1.0 - 1.4 🤔
So I what changes happen in v1.0 that make this game crash but not in v0.9.9.1?

PS: sorry for my bad english

@ghost
Copy link

ghost commented Jul 11, 2019

PPSSPP Last Build Sample Video
https://drive.google.com/file/d/1-DAgFaV7pJPyhnw4v6yNUAf0sge4kK1U/view?usp=drivesdk

PPSSPP Old Version 0.9.8 Sample Video
https://drive.google.com/file/d/1-FG1Dle59JkblSxteiekpTcHAbepIzs6/view?usp=drivesdk

*Note: ppsspp v0.9.8 has better performance without screen recording in my phone (arm32/Mali-450/octacore)

@unknownbrackets
Copy link
Collaborator

It's possible this was caused by the hardcoded use of 0x2300000000 which was recently changed. Does this still happen in the latest git builds?

Any performance issue is separate.

-[Unknown]

@hrydgard hrydgard modified the milestones: v1.9.0, v1.10.0 Aug 26, 2019
@hrydgard
Copy link
Owner

@Leopard20 can you test in the latest builds if this still happens for you?

@ghost
Copy link

ghost commented Aug 26, 2019

Still crashes on my phone same area where the game always crash I'm currently using v1.8.0-583-gc8730c933 🤷

@hrydgard
Copy link
Owner

Okay that's unfortunate, but thanks for testing!

@unknownbrackets
Copy link
Collaborator

Can you check the CRC of your disc as well? I ask because people have reported this game as "Perfect" on mobile devices:
https://report.ppsspp.org/game/ULUS10317_1.02
https://report.ppsspp.org/game/ULES00938_1.01

It seems like there are various CRCs floating around, so I just want to confirm this isn't somehow related to a bad rip. Since it's supposed to crash in the first few seconds, I imagine no one would mark it "Perfect" on mobile...

-[Unknown]

@unknownbrackets
Copy link
Collaborator

Also, if the white shading on spiderman in those screenshots is wrong (it sure looks wrong, or at least not great, to me?) a GE frame dump would help.

-[Unknown]

@sum2012
Copy link
Collaborator

sum2012 commented Jan 5, 2021 via email

@sum2012
Copy link
Collaborator

sum2012 commented Jan 25, 2021

@Leopard20 did you change cpu clock ?
In #6582 ,we see this game effect of IO (Speed)

@Leopard20
Copy link
Contributor Author

nope, I never change that.

@ghost
Copy link

ghost commented May 2, 2021

It's ok now the blue screen appears 😄
Screenshot_2020-07-15-00-48-31

This game is not crashing anymore 😭😭😭
Finally I can play and finish this game using my Redmi Note 9 both OGL and VK are running smooth on this game btw I am using latest git build of ppsspp for android 😁

@unknownbrackets
Copy link
Collaborator

I wonder if this is because the the Memory::ValidSize improvements.

-[Unknown]

@Leopard20
Copy link
Contributor Author

Leopard20 commented May 2, 2021

I wonder if this is because the the Memory::ValidSize improvements.

-[Unknown]

or maybe it's just working on that device ¯_(ツ)_/¯
there were already many devices that didn't have this problem (as you recall, #10196 (comment))

@ghost
Copy link

ghost commented May 2, 2021

Yes this is still crashing on my old phone with mali-450 gpu but not on my Redmi Note 9 and Redmi 9 🤔
IMG_20210503_013702_onFire(Abhi)

@hrydgard
Copy link
Owner

hrydgard commented May 2, 2021

So maybe there's a difference in some checking in ARM32 builds, the memory mapping we do in ARM64 not matching up perfectly with ARM32's masking perhaps? Struggling to think what the difference might be...

@Leopard20
Copy link
Contributor Author

Leopard20 commented May 2, 2021

Nope, not fixed for me either (ARM64)
Probably a driver bug?

@ghost
Copy link

ghost commented May 2, 2021

Another snapdragon phone ppsspp user is @Panderner can you reproduce this issue!?

@unknownbrackets
Copy link
Collaborator

Maybe it's somehow relying on some framebuf download?

-[Unknown]

@ghost
Copy link

ghost commented May 8, 2021

Not also crashing on Redmi 9T Qualcomm SM6115 Snapdragon 662 (11 nm) my Sister new phone

@hrydgard hrydgard modified the milestones: v1.12.0, v1.13.0 Aug 28, 2021
@ghost
Copy link

ghost commented Sep 18, 2021

Still crashing on my armv7 32bit ancient mali-450
Screenshot_2021-09-18-13-42-06

@ghost
Copy link

ghost commented Sep 19, 2021

Crashing even on IR Interpreter.
Screenshot_2021-09-19-15-25-14

@IrfanH495
Copy link

Screenshot_20220223-113229
Vulkan blue screen

@ghost
Copy link

ghost commented Sep 14, 2022

My GPU: Adreno 530 (Snapdragon 821 chipset) I think the PPSSPP version was 1.4.2-894 or something. I'll download the game later and let you know if I find anything new.

It doesn't crash on my adreno 506 🤔

@ghost
Copy link

ghost commented Mar 13, 2023

This still crashing on armv7 phone.

Interpreter
Screenshot_2023-03-14-00-09-58

Dynarec JIT
Screenshot_2023-03-14-00-04-42

IR Interpreter crashing me out the emulator without bluescreen.

@unknownbrackets
Copy link
Collaborator

Well, we have two issues that are now effectively about the same thing. I'd suggest we close one, perhaps this one. Obviously something has gone wrong if the same comment is being cross posted between two issues with almost the same title.

-[Unknown]

@peso12345gg
Copy link

يتعطل PPSSPP في الثواني القليلة الأولى من اللعبة. لا أعرف لماذا أو بالضبط متى.

(لذا فإن هذا البحث عن أعمال التهجئة البديلة: Spiderman 3).

I had a Xiaomi phone, and the game was working properly, and there was no problem, no damage, no crash

@AkiraJkr
Copy link

AkiraJkr commented May 3, 2023

Extra information from the user above:

Device that the game crashes:
Play Store Version
Android OPPO A76 (https://www.oppo.com/en/smartphones/series-a/a76/specs/)
Spider Man 3
OpenGL(Vulkan makes crashes happen faster)

According to the user, their Xiaomi Poco x3 Pro phone never had this issue. Hopefully this information is relevant.

@IrfanH495
Copy link

Screenshot_20220223-113229 Vulkan blue screen

It not crash on my device samsung m20.
I will try on sharp sh04h hopefully it not crash

@hrydgard
Copy link
Owner

Closing this as duplicate of #15825 as that one has more relevant information, even though it's newer.

@hrydgard hrydgard closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2024
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