Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4
2019.3.13f1
2020.2
Issue ID
1249172
Regression
No
Crash on buffer_add_value_full when debugging with code editor attached
How to reproduce:
1. Open the attached '1249172.zip' project
2. Open 'Main' Scene
3. Open 'CameraManager.cs' Script with Rider
4. Set a breakpoint in 76 line
5. Attach Rider Debugger to the opened project
6. Enter Play Mode
7. Press Step Out button in Rider
Reproducible with: 2018.4.23f1, 2020.2.0a14
First 5 lines of the Mac stacktrace:
#0 0x00000130cd7286 in mono_object_get_class
#1 0x00000130bdf48e in buffer_add_value_full
#2 0x00000130be45f7 in add_var
#3 0x00000130bd5907 in frame_commands
#4 0x00000130bcb3e2 in debugger_thread
#5 0x00000130cf0539 in start_wrapper
Notes:
1. When removing subscene (and then re-adding) in the Hierarchy the issue is not reproducible
2. Can't reproduce the issue on an empty project with the scenes that cause a crash
3. Video of reproduction attached in Edit
4. Reproducible when deleting Library folder
5. Reproducible with Rider, VSCode
6. Checked several projects with the identical issue, both of them had subscenes
7. Reproducible on macOS (macOS 10.14.6, 10.13.6, 10.15.4), Windows
8. Tested with Rider 2020.1.3
9. Breakpoint position doesn't influence reproduction
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a17. In certain situations the thread being inspected by the debugger would get out of sync with what was actually being inspected while stepping. This has been fixed by forcing the frames to be updated when CMD_THREAD_GET_FRAME_INFO is issued.
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b17
Resolution Note (fix version 2018.4):
Fixed in 2018.4.26f1