Search Issue Tracker

Fixed in 4.5.5

Votes

81

Found in

4.5.0f6

Issue ID

617069

Regression

No

Application crashes on Android adreno based graphics drivers

Mobile Rendering

-

Application sometimes crashes under these circumstances:

- Unity Version: 4.5.0f6
- Target Platform: Android
- Hardware: Adreno graphics drivers
- Android Versions affected: 4.1.1, 4.1.2
- Models affected (roughly ordered by # of occurrences): Andromax-c, GT-I8262, SGH-T999, HUAWEI-Y300-0100, HUAWEI-Y300-0151, LT26i, C1905, C1904, SPH-M840, C5215
- Average memory usage has been 130mb and lower on these devices.

Comments (38)

  1. Liszt

    Jan 14, 2015 15:13

    Some precision to my previous post. I paste you the stack trace :
    http://pastebin.com/3SkD0uhf

  2. Liszt

    Jan 14, 2015 15:07

    Same problem here.

    I'm on Android 4.4.4 / Sony Xperia Z3 Compact.
    If I do a build with unity 4.5.5 :
    Graphics Level : Automatic
    Device Filter ARMv7
    ==> Result : Crash

    Same thing happen with Unity 4.6.1 with Automatic and x86+ARMv7 or ARMv7 only

  3. DenisFernandes

    Jan 14, 2015 00:13

    Also confirming this bug on unity 4.6.0b21

  4. kookyoo

    Jan 13, 2015 19:44

    Still present in 4.6.1f1 on Nexus 4 device. 100% crash if Open GL mode is set to "auto". No crash if I force OpenGL ES 2.0

  5. RulerOfChaos

    Dec 31, 2014 12:51

    This is NOT fixed in Unity 4.6.1

  6. DrSchreber

    Dec 17, 2014 05:20

    I can also confirm that this is NOT fixed with 4.6.1. I even tried exporting an APK using 4.6.1p1 and forcing OpenGL ES 2.0 (with the 32-bit Display Buffer option selected) and our game still crashes on Galaxy S3 devices that are running 4.4.2. I would be incredibly appreciative if someone is willing to help out or give a suggestion as to how I might go about either fixing the issue or using some kind of work around.

  7. nburlock

    Dec 15, 2014 04:05

    I can confirm this is not fixed in 4.6.1. It is actually worse than it was in previous versions.

    At some point my app switched to Auto for Graphics Mode. This is the source of the bug I have been chasing for a while now. Setting Graphics Mode to Force GLES 2 stops the crashing. Thanks Eckhard for the workaround.

    If you want to reproduce it, buy a Moto G. Happens every time within seconds of starting an app.

  8. scritchy

    Dec 04, 2014 19:08

    +1 NOT FIXED. extremely high rate of failure. App dies at launch instantly almost. Tried upgrading to 4.5.5p5 with no change in behavior. Onsite sample device Razr M @ 4.4.2, but causing a huge wave of crashes in the real world leading to a barrage of 1 star sadness.

    12-04 14:04:39.631: E/Unity(8068): [EGL] Error:: EGL_BAD_ATTRIBUTE: An unrecognized attribute or attribute value was passed in the attribute list.

  9. eckhard

    Nov 24, 2014 14:26

    Sorry but this is NOT FIXED !

    i got plenty of Signal 11 in a very simple demo project on Samsung with A 4.4.2

    A Workaround is to set the Graphics Mode from Auto to Force GLES 2.0

  10. Daxiongmao87

    Oct 08, 2014 21:36

    Can anyone clarify if the GUI button needs to be there during the whole run-time? Or introduced only temporarily?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.