Hi After we upgrade the engine version from Unity 2022.3.60f1 to 2022.3.62f2, our game has seen an increment of the crash rate on Google Play Console, from 0.26% to 0.90%, also receive players report of crashing in the new version. From the google play console, we found all the new crashing issue …

Hi Tomas1856, Thanks for getting back to us. Yes, we released a new build yesterday by reverting the engine and using 1.3.0 patcher, we no longer see those crashing reports in this new version. However I wonder if the new patch that fix this allocation regression will be available to normal Unity…

I think this is a known regression, there’s a fix in progress, sadly there’s no public facing issue tracker link, but keep a look out for release note “Fix memory leak related to ParticleSystem job fences.” for Particles

We’re still looking, but is it possible for you get back to 2022.3.60f1 version and simply use the 1.3.0 patcher on the app ? ( CVE-2025-59489 Patcher Tool - #8 by Major_Nelson )

[image] NotDopplerDing: However I wonder if the new patch that fix this allocation regression will be available to normal Unity pro subscribers? Not as part of the regular 2022.3 LTS since that is no longer supported.

Hi, for more infomation, we also got a lot of crash on Android after upgrade the engine version from Unity 2022.3.62f1 to 2022.3.62f2. Here some of our crash log: Will it be patch with a new Unity version soon? Google Play will rejecting future app submissions using old version by December 08, 2025 …

@hloc002 I think you have a different issue, not related to the issue in this thread. Sadly without logcat I can’t say what’s wrong.

Thanks @Tomas1856 , I do have logcat could you take a look for me. Or should I move to a different discussion null pointer dereference: SIGSEGV 0x0000000000000000 #00 pc 0xd3f1c libc.so (BuildId: 899237b27ce70ad3ff85d806309243c0) #01 pc 0xeab968 libunity.so (jni::NewObject(_jclass*, _jmethodID*, …

It’s incomplete, you’re only showing stacktrace. What about error messages. Can you filter by your process id and attach full log ? Does that mean you can reproduce this locally? If so, maybe you can use Development player to get more details

“tlsf_add_pool” is a function name, it’s not an error message. In any case, 2022.3.62f2 is the last 2022.3.x LTS version, 2022.3.67 exists (which XLTS, extended LTS), but the build is only available for enterprise support customers. Like mentioned above, if you’re having issues with 2022.3.62f2, i…

Yes, thanks, I just release a build with patcher, I fear it’s still crash :sweat_smile:

Android crash rate increase after upgrade to 2022.3.62f2

Q&A for CVE-2025-59489

hloc002 October 14, 2025, 7:16am 10

Sadly I can not reproduce this locally, this stacktrace is what firebase crashlytics give me

you mean error messages like tlsf_add_pool ?

ths look like my problem, let’s move our discustion to this theard

Topic		Replies	Views
Updating Unity 2022 to Unity 6 caused a spike in libunity.so tlsf_free crashes in Firebase Crashlytics Unity Engine Burst , Advanced , Bug , 6-1	6	1168	October 18, 2025
Is there a memory leak with 2022.3.62f2? Q&A for CVE-2025-59489 Android , 2022-3-LTS , Bug	40	2283	October 31, 2025
Crash on Android after upgrade to Unity 2022.3.5f1 Questions & Answers Android , 2022-3-LTS	1	1850	October 16, 2023
Random memory related crashes in Unity versions above 2021.3.9 Unity Engine Android , Platforms , Bug	21	2672	June 20, 2024
The Windows build published with Unity 2022.3.62f3 crashes in TLSF_FREE Unity Engine Windows , 2022-3-LTS , Bug	2	91	January 6, 2026

Android crash rate increase after upgrade to 2022.3.62f2

Related topics