Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
4.5.0b4
Issue ID
594789
Regression
Yes
Motorola Droid X hangs after calling Application.Quit()
After quitting an application by calling Application.Quit() for a couple of times, the device freezes and reboots. This is not always reproducible, but happens from time to time.
Reproduced on:
Motorola Droid X (cdma_shadow) with Android 2.3.4
Not reproduced on:
Samsung Galaxy S (GT-I9000) with Android 2.3.3
Sony Ericsson Xperia Play (R800i) with Android 2.3.3
Amazon KindleFire (blaze, 1st generation) with Android 2.3.4
Motorola Droid 3 (cdma_solana) with Android 2.3.4
Motorola Droid Bionic (cdma_targa) with Android 2.3.4
Samsung Galaxy Ace Plus (GT-S7500) with Android 2.3.6
Samsung Galaxy Ace 2 (GT-I8160) with Android 2.3.6
Google Nexus One with Android 2.3.6
Sony Xperia U (ST25i) with Android 2.3.7
Reproduced with:
Unity Version 4.5.0b4 (e9e1b27aaf60)
Not reproduced with:
Unity Version 4.2.2f1 (54f0fc09defb)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
- Operations on the Color32 array are not reflected in WebGL Player when HDR is off
- Rigidbody moves away from the original GameObject when Center of Mass is set in every frame
- WebGL Player does not proceed beyond logo screen when "Target WebAssembly 2023" is enabled
Add comment