Search Issue Tracker
Fixed in 2017.4.0
Votes
0
Found in
2017.3.0a5
2017.4.12f1
2017.4.37f1
Issue ID
1135871
Regression
Yes
Profiler does not record the data when logging via scripting with Profiler.enableBinaryLog
For this to reproduce, do not record via Profiler window.
To reproduce:
1. Open attached project "prof.zip", scene main
2. Enter Play mode, and observe the console
3. Exit Play mode when logging is done
4. Go to %AppData%\LocalLow\DefaultCompany\PROF and find the file "profilerLog"
5. In Editor, load the "profilerLog" file via Profiler
Expected: data is recorded successfully when using Profiler.enableBinaryLog
Actual: data recorded fails to load to the Profiler
Reproduced in: 2017.3.0a5, 2017.4.37f1
Not reproduced in: 2017.3.0a4, 2017.4.38f1, 2018.3.14f1, 2018.4.22f1, 2019.1.14f1, 2019.2.21f1
Note: the only data that's available after loading is the count of frames that were recorded
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment