Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.4.X
Votes
1
Found in
2017.4
2018.4
2019.3.1f1
Issue ID
1221016
Regression
No
Crash on block_remove when initiating a drag and closing the window from which the drag originated
Steps to reproduce:
1. Open the attached project ("1221016.zip")
2. Use Shift + O to open the Window in the Scene View
3. Click on the window and try dragging (repeat this until the crash reproduces, usually takes less than 10 tries, occasionally up to 20)
Reproducible with: 2017.4.37f1, 2018.4.17f1, 2019.1.14f1, 2019.2.21f1, 2019.3.2f1, 2020.1.0a24
First lines of the stacktrace:
0x00007FF6D9F39F22 (Unity) block_remove
0x00007FF6D9F3A384 (Unity) tlsf_free
0x00007FF6D8398F88 (Unity) DynamicHeapAllocator::Deallocate
0x00007FF6D8394CC5 (Unity) DualThreadAllocator<DynamicHeapAllocator>::TryDeallocate
0x00007FF6D837938C (Unity) MemoryManager::Deallocate
Note:
- The issue reproduces on the first try in 2017.4, 2018.4, 2019.1, later versions usually require a few tries
Crashes on Mac, Windows, and freezes Editor UI on Linux
-
IgnisIncendio
Jun 15, 2020 15:36
Seems to still happen on Unity 2019.4.0f1 LTS.
1. Script Execution Order window
2. Quick search any script
3. Drag script into window
4. Cursor becomes "not allowed" symbol but Unity still crashes
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
- WebCamTexture does not set the requested resolution when used in WebGL
- Editor default Stylesheet/Matching Selector buttons in Debugger don't do anything
- Graphics.DrawMeshNow stops rendering Render Texture after a few frames when viewed in the Player
- New selector in Matching Selectors displays as on line -1 in debugger
- The first frames are skipped when playing a video
Resolution Note (fix version 2020.1):
Drag and drop from a closing window in the Windows Editor crash fixed in 2020.2.0a18
Resolution Note (fix version 2020.1):
Fixed in 2020.1.4f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.9f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.27f1