Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.31f1
Issue ID
UUM-54202
Regression
No
Crash on PersistentManager::InstanceIDToLocalSerializedObjectIdentifier when building on WebGL and using "URP/Nature/SpeedTree7" shader on a material
Reproduction steps:
1. Open the attached "crash_IN-56507.zip" project
2. Open the “Assets/Scenes/Menu“ Scene
3. Build the project on the WebGL platform
4. Observe the crash
Reproduced with: 2021.3.31f1
Not reproduced with: 2022.3.11f1, 2023.1.17f1, 2023.2.0b14, 2023.3.0a11
Reproduced on: Windows 10 (22H2)
Not reproduced on: No other environments tested
Note: Not able to find the “Fixed in“ version due to compilation errors and huge time consumption, 2022.1.0b1 is the lowest version I was able to test (which had no repro)
First few lines of the stack trace:
0x00007ff60aa23d3a (Unity) PersistentManager::InstanceIDToLocalSerializedObjectIdentifier
0x00007ff60a2b9c49 (Unity) TransferPPtr<StreamedBinaryWrite>
0x00007ff60c0f47fb (Unity) Shader::Transfer<StreamedBinaryWrite>
0x00007ff60aa45fcb (Unity) SerializedFile::WriteObject
0x00007ff60aa2f9cb (Unity) PersistentManager::WriteFile
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
- Inconsistent behaviour when interacting with different dropdown types with pointer events on parent Visual Element
- Hidden GameObjects won't re-enable when they have call "DontDestroyOnLoad" function
- Overlay Canvas are rendered on each split-screen camera when HDR is enabled
- [Android] The Player loses focus when using UnityEngine.Handheld.StartActivityIndicator() with Facebook SDK
- Build fails with "Building Library/Bee/artifacts/MacStandalonePlayerBuildProgram/gahcy/hj9mx3z/951.0 failed with output:..." errors when Scripting Backend is set to IL2CPP
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.