Search Issue Tracker
Fixed
Fixed in 6000.4.3f1, 6000.5.0b3, 6000.6.0a2
Votes
0
Found in
6000.0.69f1
6000.3.11f1
6000.4.0b11
6000.5.0a8
6000.6.0a2
Issue ID
UUM-137174
Regression
No
References to files from another project are not released when loading a Layout with a Locked Project window
How to reproduce:
1. Download the attached “BrokenLayout“ file and place it inside the Layouts folder (%Appdata%\Roaming\Unity\Editor-5.x\Preferences\Layouts\default)
2. Open the attached “IN-136298“ project
3. Open the Layout dropdown in the Editor toolbar and select “BrokenLayout“
4. Click on the Project window
5. Observe the Console
Actual result: NullReferenceException errors are present
Expected result: No errors are present
Reproducible with: 2023.1.0a1, 6000.0.70f1, 6000.3.11f1, 6000.4.0b12, 6000.5.0a8
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Workaround: Do not save Layouts with locked Project Browsers
Notes:
- Clicking an existing element in the Project Browser stops the errors
- Clicking an existing element is sometimes not possible, as the Project Browser can stop responding. In this case a restart of the Editor is required
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note:
Fixed in 6000.6.0a2
Resolution Note (fix version 6000.6.0a2):
Fixed in 6000.6.0a2
Resolution Note (fix version 6000.5.0b3):
Fixed in 6000.5.0b3