Search Issue Tracker
Fixed
Votes
0
Found in
4.3.4f1
Issue ID
589577
Regression
No
[debugger-protocol] Unity crashes when adding watch of GameObject.GetComponents<Component>() in MonoDevelop
To reproduce:
1) Download debuger_crash_test project and open it
2) Open Editor/Test.cs in MonoDevelop
3) Set a breakpoint in line 12
4) Attach MonoDevelop to Unity in Debug mode
5) Go to Unity and click on menu item Bug Report->Click Here
6) Go back to MonoDevelop and select View->Solution
7) In the watch window add new watch "go.GetComponents<Component>()"
8) Notice that in a couple of seconds Unity crashes
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment