Search Issue Tracker


Fixed in 2022.3.9f1, 2023.1.11f1, 2023.2.0b8, 2023.3.0a2



Found in




Issue ID




Crash on profiling::ProfilerManager::DisposeProfilerRecorder when Editor is in play mode



Reproduction steps:
1. Open the attached project “CrashRepro“ with “-debugallocator -systemallocator“ command line arguments
2. Open “Assets/Scenes/SampleScene.unity“ scene
3. Enter the Play mode
4. Wait up to a minute in the Play mode

Expected result: The Play mode continues
Actual result: Editor crashes

Reproducible with: 2022.3.6f1, 2023.1.7f1, 2023.2.0b2
Couldn’t test with: 2021.3.29f1 - “error CS0115: 'MaterialOverlayRendererFeature.SetupRenderPasses(ScriptableRenderer, in RenderingData)': no suitable method found to override“

Reproducible on: Windows 10

First few lines of stack trace:

{noformat}0x00007FF7D36136DA (Unity) profiling::ProfilerManager::DisposeProfilerRecorder
0x00007FF7D2AB009F (Unity) ProfilerRecorder_CUSTOM_Control_Injected
0x000001A702CE5375 (Mono JIT Code) (wrapper managed-to-native) Unity.Profiling.ProfilerRecorder:Control_Injected (Unity.Profiling.ProfilerRecorder&,Unity.Profiling.ProfilerRecorder/ControlOptions)
0x000001A702CE52BB (Mono JIT Code) Unity.Profiling.ProfilerRecorder:Control (Unity.Profiling.ProfilerRecorder,Unity.Profiling.ProfilerRecorder/ControlOptions)
0x000001A7037A526B (Mono JIT Code) Unity.Profiling.ProfilerRecorder:Dispose ()
0x000001A7037A4EDB (Mono JIT Code) UnityEngine.Profiling.Recorder:Finalize (){noformat}

Comments (1)

  1. MariaKhomenko

    Aug 02, 2023 11:30

    Important to note for all readers, that this crash is not exclusive to editor, it's reproduceable on all playable platforms and without “-debugallocator -systemallocator“ commands the core dump will give a random callstack related to freeing any memory, same as discussed in this thread

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.