Search Issue Tracker
Won't Fix
Won't Fix in 1.21.X
Votes
0
Found in [Package]
1.21.20
Issue ID
ADDR-3639
Regression
No
"Value cannot be null. Parameter name: _unity_self" error is logged in the Console when disposing of the UnityWebRequest in WebGL builds
Reproduction steps:
1. Open the “UITKTest” project
2. Build and run the Player (File > Build And Run)
4. In the Player, open the Browser Console and observe it
Expected result: No errors are visible
Actual result: Three "Value cannot be null. Parameter name: _unity_self" errors are displayed
Reproducible with: 1.20.10, (2021.3.35f1), 1.21.20 (2021.3.35f1, 2022.3.19f1)
Not reproducible with: 2.0.3, 2.0.8 (2023.2.11f1, 2023.3.0b8)
Reproducible on: macOS Sonoma 14.3 (Intel), Windows 10 (user’s)
Comments (1)
-
MaxxVelocity
Jul 14, 2025 16:23
This is unacceptable. If you don't know how your own system works, resign and let someone else take over who can. Unity needs to understand that we who are professionals uphold higher standards than Unity does; we are not going to accept your pathetic hand-wave. Do better.
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
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.
Resolution Note (1.21.X):
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.