Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.9.5
Issue ID
UVSB-2588
Regression
No
VisualScripting deserialization will slow the main thread when loading an AssetBundle containing a prefab with an embeded Script Machine component
How to reproduce:
1. Open the “Test.zip“ project
2. Open the “SampleScene“
3. Enter the Play Mode
4. Observe the Console
Expected result: The rectangle does not stop spinning in intervals at the beginning and “Stuck: <Time>“ is not printed in the Console window
Actual result: The rectangle stops spinning in intervals at the beginning and “Stuck: <Time>“ is printed in the Console window
Reproducible with: 1.9.4 (2022.3.57f1), 1.9.5 (2022.3.57f1, 6000.0.37f1, 6000.1.0b5, 6000.2.0a2)
Reproducible environment: macOS 15.2 (M4 Max), Windows 11 (23H2)
Not reproducible environment: No other environment tested
Notes:
- Reproducible in the Player and Editor
- The AssetBundle was built for iOS module, and the issue was tested on versions with iOS module
- The Play Mode gets stuck before all of the deserialization warnings are printed
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
- NullReferenceException is thrown when assigning an Object to a custom DebugUI.ObjectField in Rendering Debugger
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
Resolution Note:
After evaluating the impact, workaround and risk associated with fixing this issue, in addition to the current team's bandwidth and priorities, we have concluded that this issue will not be addressed in the foreseeable future.
We are closing this issue as Won’t Fix.