Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.1.X, 6000.2.X, 6000.3.X
Votes
0
Found in
6000.0.46f1
6000.1.0b14
6000.2.0a8
6000.3.0a1
Issue ID
UUM-102769
Regression
No
Unable to read data exported previously by Profiler
Reproduction steps:
1. Open any existing project
2. Open the Profiler window (Window > Analysis > Profiler)
3. Press the “Load“ button on the top right of the Profiler window
4. Select the “IN-99044_BuildTerrain.data“
Expected result: The loaded data is loaded successfully
Actual result: “Unable to read profiler data. Use Unity 6000.0.41f1 or above to inspect the data” error is thrown
Reproducible with: 6000.0.46f1, 6000.1.0b14, 6000.2.0a8
Couldn’t test with: 2022.3.61f1 (due to the error explicitly saying not to test lower versions than 6000.0.41f1)
Reproducible on: M1 Max MacOS 15.1.1
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The cursor moves into wrong place when renaming folder/asset
- Assertion error "(dx - width < padding) || (dy - height < padding)" when using Pack Preview
- [Memory Profiler] The EntryType.NativeAllocationSites_MemoryLabelIndex of snapshots only reports -1 or 0 instead of the MemLabel used for allocations made from any call site.
- [Vulkan] Artifacts appear in the Player when using Screen Space shadows with orthographic camera
- Errors OnGUIDepth changed & GUIUtility:ProcessEvent when opening Textures with Third Party App
Add comment