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
- Color picker does not show the correct color when selecting color on the moving object
- “Asset X has no meta file, but it's in an immutable folder. The asset will be ignored.” errors are thrown when importing package with files not listed in package.json's "files" property
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
Add comment