Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
Votes
0
Found in
2018.3.0a8
2018.3.8f1
Issue ID
1150495
Regression
No
Saving Profiler Data does not save Markers Metadata
To reproduce:
1. Open Unity and create a New Project
2. Open "SampleScene" scene
3. Open Build Settings and check Development Build and Autoconnect Profiler
4. Build and Run the project on Standalone, iOS or Android
5. When Project is built Profile several frames - in this case, find "File.Read" Marker and observe that it has Metadata
6. Save Profiler Data
7. Clear Profiler Data from Profiler Window
8. Load previously saved Profiler Data
9. Find "File.Read" Marker
Expected results: "File.Read" Marker still has Metadata
Actual results: "File.Read" Marker shows his Name and the Duration but no Metadata ("File.Read" should include info about the filename)
Notes:
- This issue appears on Windows Standalone, macOS Standalone, iOS, and Android
- Metadata is not available only when reloading a capture from file
- Images of Expected and Actual results are shared in the Comments section
Reproduced on Unity 2018.3.0a8, 2018.3.14f1, 2018.4.0f1, 2019.1.2f1, 2019.2.0a14 and 2019.3.0a1
Not reproduced on Unity 2018.3.0a7
Regression on Unity 2018.3.0a8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment