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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
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.