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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
allan_nava
Nov 13, 2017 20:04
I have the same issue