Android crash in Unity 6 (6000.2.8f1) — mostly low-end devices Android 13–15. Fixed in newer 6000.2.x?

[groot_unity]

Hi folks,

We’re investigating an Android crash reported in Google Play Console / Firebase Crashlytics, and I’m trying to confirm whether:

Crash distribution (from Play Console)

• Android versions affected: mostly Android 13 (SDK 33), Android 14 (SDK 34), Android 15 (SDK 35) (also some Android 11 / other)
• Top affected devices include:
  • Samsung a05s
  • Motorola rhode
  • Redmi xun / Redmi spes
• Common chipset shown: QTI SM6225
• RAM around 4GB on many of the top devices

1. this is a known Unity 6 issue fixed in a newer 6000.2 patch, or
2. other devs have seen something similar on the same Android versions / chipsets.

Project / Engine

• Unity version: 6000.2.8f1 (Unity 6)
• Platform: Android
• Crash source: Google Play Console + Firebase Crashlytics

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 23901 >>> kr.co.smartstudy.bebefinntown_android_googlemarket <<<

backtrace:
  #00  pc 0x000000000008bbf8  /apex/com.android.runtime/lib64/bionic/libc.so (__memcpy_aarch64_simd+248)
  #01  pc 0x0000000000ed580c  /data/app/~~4C32oj-Bzs7cI51Q62FOuQ==/kr.co.smartstudy.bebefinntown_android_googlemarket--3k5iG4VK2dPginj3l-UmQ==/lib/arm64/libunity.so (BuildId: 6466a170926546ea)
  #02  pc 0x00000000010a0f5c  /data/app/~~4C32oj-Bzs7cI51Q62FOuQ==/kr.co.smartstudy.bebefinntown_android_googlemarket--3k5iG4VK2dPginj3l-UmQ==/lib/arm64/libunity.so (BuildId: 6466a170926546ea)
  #03  pc 0x0000000001099514  /data/app/~~4C32oj-Bzs7cI51Q62FOuQ==/kr.co.smartstudy.bebefinntown_android_googlemarket--3k5iG4VK2dPginj3l-UmQ==/lib/arm64/libunity.so (BuildId: 6466a170926546ea)
  #04  pc 0x00000000010991dc  /data/app/~~4C32oj-Bzs7cI51Q62FOuQ==/kr.co.smartstudy.bebefinntown_android_googlemarket--3k5iG4VK2dPginj3l-UmQ==/lib/arm64/libunity.so (BuildId: 6466a170926546ea)
  #05  pc 0x00000000007b8918  /data/app/~~4C32oj-Bzs7cI51Q62FOuQ==/kr.co.smartstudy.bebefinntown_android_googlemarket--3k5iG4VK2dPginj3l-UmQ==/lib/arm64/libunity.so (BuildId: 6466a170926546ea)
  #06  pc 0x00000000000f82d8  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+208)
  #07  pc 0x0000000000094d78  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)

Has anyone run into a similar issue? If you know any fixes or workarounds, I’d really appreciate it if you could share. Thanks in advance!

[manugil]

Please, symbolicate the crash for us to be able to get more context.

Also, Using symbols in the Google Play console will help you get more context on this type of crashes.

[groot_unity]

Hello, thank you for the helpful guidance.

I’m sharing the crash call stack information using addr2line.

We are currently using Unity 6000.2.8f1, and we’re considering moving to an LTS version.

Do you have any other possible solutions or recommendations?

jin@gangjin-yeong-ui-MacBookPro bin % ./llvm-addr2line -f -C -e libunity.sym.so  0x0000000000ed580c 
VFXBatch::VFXBatch(unsigned int, VFXBatchedEffect const&)
??:0
jin@gangjin-yeong-ui-MacBookPro bin % ./llvm-addr2line -f -C -e libunity.sym.so  0x00000000010a0f5c  
void InstancingProps::FillInstanceBufferDispatchConstants<Instancing::DrawAPIArgs>(void* const*, unsigned int, unsigned int, ShaderPropertySheet const&, Instancing::DrawAPIArgs const&) const
??:0
jin@gangjin-yeong-ui-MacBookPro bin % ./llvm-addr2line -f -C -e libunity.sym.so  0x0000000001099514
void InstancingProps::FillInstanceBufferDispatchConstants<Instancing::RenderLoopArgs>(void* const*, unsigned int, unsigned int, ShaderPropertySheet const&, Instancing::RenderLoopArgs const&) const
??:0
jin@gangjin-yeong-ui-MacBookPro bin % ./llvm-addr2line -f -C -e libunity.sym.so  0x00000000010991dc
void InstancingProps::FillInstanceBufferDispatchConstants<Instancing::RenderLoopArgs>(void* const*, unsigned int, unsigned int, ShaderPropertySheet const&, Instancing::RenderLoopArgs const&) const
??:0
jin@gangjin-yeong-ui-MacBookPro bin % ./llvm-addr2line -f -C -e libunity.sym.so  0x00000000007b8918
CalculateFocusedLightHull(Vector3f const*, Vector3f const&, MinMaxAABB const&, core::vector<Vector3f, core::allocator<Vector3f, 0ul>>&)
??:0
jin@gangjin-yeong-ui-MacBookPro bin % 

VFXBatch::VFXBatch(unsigned int, VFXBatchedEffect const&)
void InstancingProps::FillInstanceBufferDispatchConstants<Instancing::DrawAPIArgs>(void* const*, 
void InstancingProps::FillInstanceBufferDispatchConstants<Instancing::RenderLoopArgs>(void* const*, 
CalculateFocusedLightHull(Vector3f const*, Vector3f const&, MinMaxAABB const&,

Regards,

Derrick

[rubix1991]

I think you better use Stacktrace Utility | Android Logcat | 1.2.3 , since it validates if symbol file matches the address (by using build id), in your case it’s possible you’re using incorrect symbol file, and thus resolving stacktrace incorrectly.