Search Issue Tracker
Fixed in 2017.2.0f3
Votes
1
Found in
2017.1.1p1
Issue ID
955994
Regression
Yes
[Profiler] Unity 2017.2 crashes when loading profiling data saved from 2017.1
Unity 2017.2 crashes if profiling data saved from 2017.1 is loaded
Quick repro:
1. Start 2017.2 (.0f2)
2. Open the Window->Profiler
3. Click Load
4. In the project folder, go to the Builds folder
5. Select the file test.data and click open
6. Observe Unity crashes
Full Repro:
1. Open a 2017.1 version
2. Load the attached project 'profiler_test'
3. Build the Player (make sure auto connect profiler is enabled in the build setttings)
4. Start the player
5. Open the Window->Profiler
6. Click Record and record for a bit
7. Stop recording
8. Click Save and save the profiling data
9. follow the steps in the quick repro above
Tested with Unity versions:
2017.1.1p1, 2017.2.0f2
Comments (1)
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
- [Linux] Navigating Prefab Components in Overrides window shows rendering artifacts in the Editor
- Prefab Overrides window cuts-off Component labels across multiple Components
- Opening Memory Settings documentation from Project Settings window opens missing page
- Animated GameObjects ignore Shader keywords when running on VisionOS Player with Polyspatial
- Quickly clicking "Open query in Search Window" in the Hierarchy twice opens the two Search tabs at the same time
allan_nava
Nov 13, 2017 20:04
I have the same issue