Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0a7
Issue ID
950665
Regression
No
[OSX][Legacy runtime] Editor crashes after attaching VS debugger few times
[OSX][Legacy runtime] Editor crashes after attaching VS debugger few times
1. What happened
Similar to case 941204, but with the old runtime. Also, you have to click Start/Stop debugging button much faster, like 3-4 times/second.
2. How we can reproduce it using the example you attached
- Attached is an empty project with 1 default script.
- Open script in VS
- Start clicking 'Play'/'Stop' debugger btn in VS to attach/detach debugger very fast
- Continue for a few seconds
>>> Crash.
Usually, only OSX crash reporter is invoked, but this time Unity Bug Reporter was launched as well.
Editor log ends with:
=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
This is reproducible in 2017.3.0a7, 2017.2.0b11, 2017.1.1p2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Source Image property gets set to 'None' when using a specific Sprite and Play mode is entered
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
Add comment