Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.4
2018.4.24f1
Issue ID
1311847
Regression
No
[Profiler] Crash on profiling::Profiler::StartNewFrameSeparateThread
Reproduction steps:
-Due to the nature of this crash, there is no way currently to reproduce it
Reproducible with, according to user reports 2018.4.11f1, 2018.4.24f1
Analyzed causes of a handful of crashes with the same characteristics:
-code change
-opening the Profiler Window
-switching focus back to Editor
-stoping or starting Profiler recording
-entering Play Mode after code change
-enabling Deep Profiling
-clearing Profiling data
Stacktrace:
#0 0x00000100f2a558 in profiling::Profiler::StartNewFrameSeparateThread(profiling::PerThreadProfiler, unsigned long long, unsigned int)
#1 0x00000100d7b716 in PreloadManager::Run()
#2 0x00000100d7b64e in PreloadManager::Run(void)
#3 0x00000100e81292 in Thread::RunThreadWrapper(void*)
#4 0x007fff6fd69109 in _pthread_start
#5 0x007fff6fd64b8b in thread_start
Notes:
-Usually a one time issue
-One instance reports a crash occurring on macOS
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
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
Resolution Note:
Due to the nature of this crash, there is no way currently to reproduce it
If you would happen to find some steps or a project which reproduces this issue consistently, we would be very grateful.