Search Issue Tracker
Not Reproducible
Votes
4
Found in
5.0.0f4
Issue ID
675596
Regression
No
[iOS] Coroutine never resumes if a WWW request is disposed after 'yield return WWW'
To Reproduce:
1.Open WWW_Dispose_Repro.zip (attached to the comment)
2. Run it in editor, observe that (YieldReturnTest.cs):
-in StartWWW a WWW request is created & the coroutine is paused with "yield return _www";
-StopWWW is called & it disposes the WWW request.
-execution returns to StartWWW & the Debug.Log statement is executed.
3. Deploy it to device and observe that after the WWW is disposed the StartWWW never resumes and the Debug.Log statement is never called.
The behavior is the same even if StopWWW call is delayed (comment line 18, uncomment 25 ).
If the WWW is not disposed, StartWWW resumes as expected.
Reproduced with: 4.3.4f1, 4.6.3p1, 5.0.0f4
Comments (1)
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
eyalfx
Mar 27, 2015 05:44
I can't even run a simple www on device. even though it's working in editor.
But my issue is only with 5.00f4. works fine in 4.3.6p2