Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X, 2022.1.X
Votes
0
Found in
2019.4
2019.4.29f1
2020.3
2021.2
2022.1
Issue ID
1386532
Regression
Yes
[Memory Profiler] Capturing Player built with higher Unity version crashes the Editor
How to reproduce:
1. Create a new 3D project using 2022.1.0b1
2. Enable Development Build and Autoconnect Profiler in Build Settings (File > Build Settings)
3. Build And Run
4. Close the Editor
5. Create a new 3D project using a version from “Reproducible with” list
6. Install Memory Profiler package
7. Open Memory Profiler window (Window > Analysis > Memory Profiler)
8. Change target from the Editor to the Player
9. Click Capture
Expected result: Memory snapshot gets captured
Actual result: Editor crashes
Reproducible with 0.2.10-preview.1 (2019.4.34f1), 0.4.2-preview.1 (2019.4.34f1, 2020.3.25f1, 2021.2.6f1 2022.1.0a5)
Not reproducible with: 0.4.2-preview.1(2022.1.0a6, 2022.1.0b1)
Notes:
- Reproducible with macOS build
Stack trace:
0x00007FF76871A519 (Unity) MemoryManager::GetAllocatedMemory
0x00007FF7694D3E95 (Unity) MemorySnapshotProcess::ProcessNativeMemoryLabels
0x00007FF7694D35BA (Unity) MemorySnapshotProcess::Process
0x00007FF7694D2BAA (Unity) MemorySnapshotOperation::MemorySnapshotDeserializeThread
0x00007FF76948D873 (Unity) Thread::RunThreadWrapper
0x00007FFADBAD7034 (KERNEL32) BaseThreadInitThunk
0x00007FFADDA02651 (ntdll) RtlUserThreadStart
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
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b7
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.9f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.28f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.36f1