Search Issue Tracker
Fixed
Fixed in 6000.0.63f1, 6000.2.13f1, 6000.3.0b11, 6000.4.0a5, 6000.5.0a1
Votes
0
Found in
6000.0.56f1
6000.2.2f1
6000.3.0a6
6000.4.0a1
Issue ID
UUM-116010
Regression
No
Crash on RendererScene::NotifyInvisible when entering Play mode after undoing a change within the scene with Ctrl+z
How to reproduce:
1. Open the attached “IN-109345” project
2. Open the “Home” Scene
3. In the Hierarchy, select the “Game Room Light 1” GameObject
4. Change the Light Type in the Inspector to “Point”
5. Undo step 4 by pressing Ctrl+z
6. Enter Play mode
7. Observe the crash
Or with a fresh project:
1. Create a new project
2. Add a Cube to the scene (GameObject > 3D Objects > Cube)
3. Undo step 2 (Ctrl+z)
4. Enter Play mode
5. Observe the crash
Reproducible with: 2023.1.0a1, 6000.0.56f1, 6000.2.2f1, 6000.3.0a6
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Note: Reproduction can be inconsistent in a fresh project
First few lines of the StackTrace:
0x00007FFC57D62EC7 (Unity) RendererScene::NotifyInvisible
0x00007FFC58121A37 (Unity) `InitPlayerLoopCallbacks'::`2'::EarlyUpdateRendererNotifyInvisibleRegistrator::Forward
0x00007FFC580F0AD7 (Unity) ExecutePlayerLoop
0x00007FFC580F0C47 (Unity) ExecutePlayerLoop
0x00007FFC580F5D21 (Unity) PlayerLoop
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note (fix version 6000.5.0a1):
Invalid reference was created when undoing changing the light type if cached shadows are enabled. This caused a crash because of the cached shadow book keeping not cleaning up after an undo operation causing an invalid reference to be used.
Resolution Note (fix version 6000.4.0a5):
Invalid reference was created when undoing changing the light type if cached shadows are enabled. This caused a crash because of the cached shadow book keeping not cleaning up after an undo operation causing an invalid reference to be used.
Resolution Note (fix version 6000.3.0b11):
Invalid reference was created when undoing changing the light type if cached shadows are enabled. This caused a crash because of the cached shadow book keeping not cleaning up after an undo operation causing an invalid reference to be used.
Resolution Note (fix version 6000.2.13f1):
Invalid reference was created when undoing changing the light type if cached shadows are enabled. This caused a crash because of the cached shadow book keeping not cleaning up after an undo operation causing an invalid reference to be used.
Resolution Note (fix version 6000.0.63f1):
Invalid reference was created when undoing changing the light type if cached shadows are enabled. This caused a crash because of the cached shadow book keeping not cleaning up after an undo operation causing an invalid reference to be used.