Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
1
Found in
2019.1.0a12
Issue ID
1111490
Regression
Yes
[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
Environment:
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 (2)
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
R0hit97
Sep 13, 2019 06:25
Using Unity 2019.2.0f1 still getting this error.
2019-09-13 11:07:10.442 5626-5642/? E/AndroidRuntime: FATAL EXCEPTION: UnityMain
Process: com.YouthBuzz.VRC1, PID: 5626
java.lang.Error: FATAL EXCEPTION [UnityMain]
Unity version : 2019.2.0f1
Device model : Oculus Pacific
Device fingerprint: oculus/vr_pacific/pacific:7.1.1/NGI77B/358570.6130.0:user/release-keys
Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000220
Build fingerprint: 'oculus/vr_pacific/pacific:7.1.1/NGI77B/358570.6130.0:user/release-keys'
Revision: '0'
pid: 5626, tid: 5816, name: Thread-15 >>> com.YouthBuzz.VRC1 <<<
r0 00000000 r1 aaaaaaab r2 00000000 r3 c9cff0c8
r4 cd15d790 r5 c9df3490 r6 00000000 r7 00000001
r8 c9df3494 r9 00000000 sl c53a1800 fp c00c2870
ip efdcf868 sp c00c2788 lr efd9b833 pc c04ca134 cpsr c860f480
at Horizon.00061134(Native Method)
at libc.je_arena_tcache_fill_small(je_arena_tcache_fill_small:310)
harshdevchandel
Jul 29, 2019 10:09
i am slo getting same issue on samsung m30