Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.5.0a9
6000.6.0a1
Issue ID
UUM-137939
Regression
Yes
NullReferenceException and Lifecycle errors appear after Editor Theme change with Rendering Debugger active
Steps to reproduce:
- Create a project
- Install Unity AI (2.3.0-pre.2)
- Go to "Window -> Analysis -> Rendering Debugger"
- Expand the "Lighting Features" drop-down in the "Frequently Used" window
- Instead of "Nothing" select "Everything"
- Update Unity theme (Unity -> Settings -> General -> Editor Theme)
- Open Console window
Actual results: Console window displays 4 errors:
{code:java}
Lifecycle ERROR : Cannot exit scope of type 'TScope', no active scope of that type found
UnityEngine.DomainReloadLifecycleController/ScriptingCoreDebugForIl2AndMonoCpp:LogError (string) {code}
{code:java}
Lifecycle ERROR : Cannot exit scope of type 'TScope', no active scope of that type found UnityEngine.DomainReloadLifecycleController/ScriptingCoreDebugForIl2AndMonoCpp:LogError (string)
{code}
{code:java}
Lifecycle ERROR : Failed to exit assembly loaded scope, due to exception System.NullReferenceException: Object reference not set to an instance of an object
at Unity.Scripting.LifecycleManagement.LifecycleController.ExitScope[TContext] (Unity.Scripting.LifecycleManagement.LifecycleScopeWithContext`1[T] scope) [0x00014] in /Users/bokken/build/output/unity/unity/External/ScriptingCore/Unity.Scripting/LifecycleManagement/LifecycleController.cs:301 {code}
{code:java}
NullReferenceException: Object reference not set to an instance of an object
Unity.Scripting.LifecycleManagement.LifecycleController.ExitScope[TContext] (Unity.Scripting.LifecycleManagement.LifecycleScopeWithContext`1[T] scope) (at /Users/bokken/build/output/unity/unity/External/ScriptingCore/Unity.Scripting/LifecycleManagement/LifecycleController.cs:301) {code}
Expected results: No errors
Reproducible with versions: 6000.5.0a9{},{} 6000.6.0a1
Not reproducible with versions: 6000.4.1f1, 6000.5.0a8
Can’t test with versions: 6000.5.0a1 - 6000.5.0a7, as AI can not be installed. A screenshot has been added to the Attachments section.
Tested on (OS): macOS - Tahoe 26.3.1
Notes: Errors become visible during the first Unity theme change. Sometimes several changes are needed. On the 6000.5.0a8 build, I am getting a different set of errors. A screenshot has been added to the Attachments section.
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
Add comment