Search Issue Tracker
Won't Fix
Votes
5
Found in
2021.3.40f1
2022.3.36f1
6000.0.9f1
6000.2.0a1
6000.3.0a1
Issue ID
UUM-96971
Regression
No
Editor hangs on Domain Reload when there is recursion in SerializeReference class structure
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/InfiniteReloadDomain.unity” Scene
3. Open the context menu of “Assets/InfiniteReloadDomain.cs” Script and select “Reimport”
Expected result: The Editor completes Domain Reload or a warning message is logged
Actual result: The Editor hangs on Domain Reload
Reproducible with: 2021.3.40f1, 2022.3.36f1, 6000.0.9f1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Comments (2)
-
mitaywalle
Oct 08, 2024 11:52
also RAM infinitely expand during this event
-
mitaywalle
Oct 08, 2024 11:50
also reproducible with 6000.0.17f1 and 6000.0.22f1
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.