Search Issue Tracker
Won't Fix
Won't Fix in 3.0.X
Votes
4
Found in [Package]
3.0.15
Issue ID
RIDER-41
Regression
Yes
"Unloading broken assembly" error appears when opening a project in Safe Mode with a Script error
Reproduction steps:
1. Open the attached “Repro“ project in Safe Mode (press the “Enter Safe Mode“ on the pop-up)
2. Observe the Console window
Expected result: Only the “error CS0117: 'Debug' does not contain a definition for 'Lo'“ error is present
Actual result: “Unloading broken assembly Library/ScriptAssemblies/Unity.Rider.Editor.dll, this assembly can cause crashes in the runtime“ error appears in addition to the Script error
Reproducible with: 3.0.25, 3.0.26 (2021.3.32f1, 2022.3.14f1, 2023.2.1f1, 2023.3.0a15)
Not reproducible with: 2.0.7, 3.0.24 (2021.3.32f1, 2023.3.0a15)
Reproducible on: Windows 10 Pro (22H2), M1 MacOs 14.0
Not reproducible on: No other environment tested
Comments (2)
-
Mikaeli
Dec 28, 2023 22:10
Reproducible in 2023.2.2f1 windows pro (22H2)
Ran into the issues trying to work with Unity Learn project: unity-fv-ip-starboss-master
SAFE-MODE
-
Th3Vale
Nov 26, 2023 08:46
same issue
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Not reproducible anymore
Resolution Note (3.0.X):
Not reproducible anymore