Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0a7
Issue ID
605396
Regression
Yes
User can not close down a custom editor window from a previous project
User can not close down a custom editor window from a previous project.
To reproduce:
- Import attached "TestWindow.unitypackage" and launch "test" scene
- Go to "Test" in top menu bar an select "CurveField Test"
- Dock the "Test Window" somewhere in the editor
- Save the "test" scene
- Create a new project
- Observe that there is a "Failed to load" window
- Right-click on the tab and observe that nothing happens
- Observe alse the following error in Console:
"Recursive Serialization is not supported. You can't dereference a PPtr while loading. (Constructors of C# classes may not load objects either eg. EditorGUIUtility.TextContent should be moved to OnEnable. See stacktrace.)
UnityEditorInternal.InternalEditorUtility:LoadSerializedFileAndForget(String)
UnityEditor.WindowLayout:LoadWindowLayout(String, Boolean)"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment