Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.4.X, 2018.1.X
Votes
0
Found in
2017.3.0p4
Issue ID
1011626
Regression
Yes
[2017.3][Memory Profiler][.NET 3.5] Taking a Snapshot when using .NET 3.5 crashes App
To reproduce:
1. Download attached project "2017-3_BigProject_Updated.zip" and open in Unity
2. Set "Scripting Runtime Version" to .NET 4.6
3. Build and run the project on an Android device
4. Connect to Unity's Profiler
5. Open the Memory Profiler and press the "Take Snapshot" button
Note: Observe that it takes Snapshot and see that APK does not crash
6. Close APK
7. Set "Scripting Runtime Version" to .NET 3.5
3. Build and run the project on an Android device
8. Connect to Unity's Profiler
9. Open the Memory Profiler and press the "Take Snapshot" button
Note: Observe that APK crashed
Notes:
- Logcat is shared in the comments section
Devices:
- Google Pixel 2, OS: 8.1.0, CPU: arm64-v8a, GPU: Adreno (TM) 540
- iPhone 7, iOS 11.0
Reproduced on Unity 2017.3.0p2 and 2017.3.1p4
Not reproduced on Unity 2017.3.0p1, 2018.1.0b11 and 2018.2.0a2
Regression on Unity 2017.3.0p2
Could not check is this fixed because in Unity 2018.2.0a3 and 2018.2.0a4 project fails in building
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment