Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2017.4.X, 2018.4.X, 2019.1.X
Votes
0
Found in
2017.4.0f1
2017.4.13f1
Issue ID
1117213
Regression
No
ArgumentNullException is thrown when yielding and disposing a WWW object
To reproduce:
1. Download attached project “project_610124.zip" and open in Unity
2. Open “scene” scene
3. Enter to Play mode
4. Observe that ArgumentNullException is thrown in Console:
"ArgumentNullException: Argument cannot be null.
Parameter name: _unity_self
UnityEngine.WWW.get_keepWaiting () (at /Users/builduser/buildslave/unity/build/Modules/UnityWebRequestWWW/Public/WWW.cs:316)
UnityEngine.CustomYieldInstruction.MoveNext () (at /Users/builduser/buildslave/unity/build/Runtime/Export/CustomYieldInstruction.cs:19)
UnityEngine.SetupCoroutine.InvokeMoveNext (IEnumerator enumerator, IntPtr returnValueAddress) (at /Users/builduser/buildslave/unity/build/Runtime/Export/Coroutines.cs:17)"
Notes:
- This issue appears on both Windows and macOS
- It seems that this issue was fixed in Unity 2017.2: https://issuetracker.unity3d.com/issues/nullreferenceexception-is-thrown-when-the-dispose-method-is-inside-the-using-block
Reproduced on Unity 2017.4.0f1, 2017.4.17f1, 2018.2.20f1, 2018.3.3f1, 2019.1.0a14 and 2019.2.0a1
Comments (4)
-
vbelkin
Nov 20, 2020 23:50
Reproduced in 2019.4.14f1
-
miksol31
Jul 19, 2019 15:30
Fix for LTS
-
Eldirfar
Feb 28, 2019 13:44
Fix for LTS?
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2019.2):
Fixed in 2019.2a3