Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2020.1.0b9
Issue ID
1253117
Regression
No
Crash ProfilerDriver_CUSTOM_SaveProfile on saving data from Profiler
Does not reproduce every time.
1. Start Deep profiling of Editor.
2. Enter playmode.
3. Wait or some time and save profiled data.
Actual result: Editor crashes with stack trace:
Crash is found in case editor_prev_log log:
DynamicHeapAllocator::Allocate
MemoryManager::Allocate
MemoryManager::ReallocateFallbackToAllocateDeallocate
MemoryManager::Reallocate
realloc_internal
dynamic_array_detail::dynamic_array_data::resize_buffer
SerializeProfilerInformation
ProfilerFrameData::Serialize const
profiling::ProfilerSession::SaveToFile
ProfilerDriver_CUSTOM_SaveProfile
UnityEditorInternal.ProfilerDriver:SaveProfile (string) {0x7f98cad7c098}
More on Crash Analyzer: https://crashes.hq.unity3d.com/crashes/5ed8c56abbc51300014c68cd
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes when debugging a for loop
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
Add comment