Search Issue Tracker

Fixed in 2019.2

Fixed in 2018.3, 2019.1



Found in


Issue ID




[Android] Build crashes on device with '.NET 4.x Equivalent' Scripting version when Stripping level set to low / medium / high



Build crashes on a device with '.NET 4.x Equivalent' Scripting runtime version when Stripping level set to low / medium / high.

Steps to reproduce:
1. Open an attached project or create a new one.
2. Switch platform to Android and go to player settings.
3. Check Scripting Runtime version is set to '.NET 4.x Equivalent', Scripting backend is 'Mono'
4. Stripping level set to low/medium/high.
5. Click build and run or make a build and deploy it in a device.

Note: Device Stack trace file attached for reference

Actual Result:
Build crashes on the device.

Expected Result:
Build runs without crash.

Occurring On: 2019.1.0a13, 2019.1.0a12
Working fine On: 2019.1.0a11, 2018.3.0f2

Windows and Mac

Verified on: Samsung Galaxy S9 (8.0.0), Google Pixel XL (7.1.2), Meizu MX5 (5.0.1)

Crash Stack:

========== OUTPUTTING STACK TRACE ==================

java.lang.Error: FATAL EXCEPTION [UnityMain]
Unity version : 2019.1.0a13
Device model : Google Pixel XL
Device fingerprint: google/marlin/marlin:7.1.2/NJH47D/4045516:user/release-keys

Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
Build fingerprint: 'google/marlin/marlin:7.1.2/NJH47D/4045516:user/release-keys'
Revision: '0'
pid: 10760, tid: 10775, name: UnityMain >>> com.Unit.xyzz <<<
r0 00000000 r1 00000000 r2 00000000 r3 ed5fe2ec
r4 ed5fe2ec r5 00000000 r6 00000000 r7 d2caf1b8
r8 d3180250 r9 000000ff sl 00000003 fp ed5fe108
ip d2e7a7e0 sp ed5fdf40 lr d2d7c9ec pc d29ba7bc cpsr 00002a17

at libmonobdwgc-2.000727bc(Native Method)
at libmonobdwgc-2.00367388(Native Method)
at libmonobdwgc-2.mono_runtime_try_invoke(mono_runtime_try_invoke:196)
at libmonobdwgc-2.mono_runtime_invoke(mono_runtime_invoke:92)

========== END OF STACKTRACE ==================

Comments (1)

  1. 20afb152498160cd709c2f400537c84c?d=mm


    Jul 29, 2019 10:09

    i am slo getting same issue on samsung m30

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.