Search Issue Tracker
Fixed in 2020.2
Fixed in 2018.4, 2019.4, 2020.1
Votes
61
Found in
2018.4
2019.4
2019.4.12f1
2020.1
2020.2
2021.1
Issue ID
1284525
Regression
No
[Android][IL2CPP] App crashes during launch with "Using memoryadresses from more than 16GB of memory" messages on Android 11
Repro steps:
1. Create a new project
2. Switch build target to Android
3. Set Scripting Backend to IL2CPP and Target Architecture to ARM64
4. Build and Run on Android (might need to be flashed with HWASan)
Actual: App crashes on launch before the splash screen
Reproducible with: 2018.4.28f1, 2019.4.13f1. 2020.1.10f1, 2020.2.0b8, 2021.1.0a1
Tested and reproduced on:
Google Pixel 3 XL - (AOSP on crosshatch), Android 11, CPU: Qualcomm SDM845 Snapdragon 845, GPU: Adreno (TM) 630
Didn't reproduce on:
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00318, Oneplus 7Pro (GM1913), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
N/A, Oneplus OnePlus 6 (ONEPLUS A6003), Android 10, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
Notes:
- Didn't reproduce on factory Android 11 with an empty project
- Reproduces only when targeting ARM64
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
- [Encoding/compression] Lightmap compression artifacts when Build Target = Android, Lightmap Encoding = Low
- Public Spaceship demo errors due to missing prefabs and references on 2020.1
- Integer properties do not show up in Frame Debugger
- Animated Object merges with another Object in an Animation
- Video Script Playable Track not working as expected -- cannot properly manipulate video from timeline
erikhallgren
Nov 16, 2020 21:17
Is this fixed or not?
From the release notes
Known Issues in 2020.1.13f1:
...
- Mobile: [Android][IL2CPP] App crashes during launch with "Using memoryadresses from more than 16GB of memory" messages on Android 11
...
eladleb4
Nov 12, 2020 14:15
I can see it is listed as fixed in 2019.4, but which 2019.4 are we talking about..?
2019.4.14 was released on November 5th 2020 and yesterday this wasn't marked as fixed.
So is it 2019.4.15 ?
When writing these lines 2019.4.15 isn't out, so why is marked as fixed..?
SaturnCO
Nov 11, 2020 21:06
Why does it say fixed in 2020.1 yet on 2020.1.13f1 (The lastest) it's listed as a known issue?
Please prioritize fixing this as I'm already getting bad reviews from crash on launch from android 11 users.
The_Taj
Nov 11, 2020 19:07
I see that this issue is listed as fixed in 2020.1, but checking the release notes for the 2020.1.13f1 this is still listed as a known issue.
I've also tested upgrading and can confirm this issue is not fixed in 2020.1.13f1.
Is this listing as 'fixed' incorrect, or do I need to wait for a new 2020.1 version?
taledeveloper
Nov 02, 2020 07:31
I got the same issue
DurmusAli
Oct 27, 2020 11:56
We are facing the similar issue here. On our side reports are all from Android 11 and Google Pixel phones.
ol1ph4nt
Oct 20, 2020 02:42
We are facing the same issue here using Unity 2019.4.12f1 on Android 11 on Pixel 2.
Similar crashlog and similar issue crashing soon after launching the game.
Although, in our case, crash only seem to happen when quickly trying to interact with the game.
If instead, we let the game run for 10 seconds, then the crash won't happen.
johannthb
Oct 19, 2020 11:06
Do you have any updates on this issue?
We believe that this issue is affecting many (maybe all) developers that are using Unity on Android, and will only increase in severity as Android 11 becomes more widespread.
We've added more context on our situation in this forum post if it helps: https://forum.unity.com/threads/android-11-il2cpp-arm64-crash-in-unity-lts-2019-4-12f1.986883/