Search Issue Tracker
By Design
Votes
5
Found in
5.3.4f1
Issue ID
787526
Regression
No
[Android] [Crash] Crash on some Samsung Galaxy S3 devices when loading the first scene
Reproduction steps:
1) Open attached project
2) Build and run on an Android device
--- Only got repro with T-Mobile Samsung Galaxy S3
--- Build will crash after the splash screen
Workaround: The project uses many big default-compressed (ETC2) RGBA textures and it runs out of memory. Using ATC textures saves a lot of memory and project doesn't crash.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Seanm07
May 17, 2016 15:01
Also had this happen in our app built on 5.3.4f1 on Galaxy S3 devices. It doesn't seem to happen every time but I reproduced it on a few S3 test devices on the Samsung Remote Lab testing service (got it to happen 1-2 times then it wouldn't crash again, seemed to get further on later launches too) however I then couldn't replicate it on our local S3 even though all devices were exactly the same with the same android version (4.3)
Here's the raw exported logcat when the crash happened on the Samsung's Remote Test Lab: http://pastebin.com/rXeXYX9d