Search Issue Tracker
By Design
Votes
0
Found in
5.0.0b22
Issue ID
670942
Regression
No
WWW.bytesDownloaded freezes application
1. Open scene "Main Scene".
2. Open script "Installer".
1. In line 35 add "download.bytesDownloaded".
3. Play scene.
4. FREEZE!
Reproduced: 5.0.0f1, 5.0.0b15, 4.6.0f1
Comments (2)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
liortal
Jul 31, 2017 05:40
Why is this by design? can anyone comment on this bug ? also, is this behaviour only seen in the editor, or also when running on devices ?
TechCor
Jun 13, 2015 08:06
This is a duplicate of issue 572719, which is still active.
Why is the resolution "By Design"? When is freezing the application by design?
Developers expect www.BytesDownloaded to return the current number of bytes downloaded while it is in progress. It shouldn't block until the download is finished.
If Unity really doesn't want to provide what developers expect, www.BytesDownloaded should throw an exception if the download isn't finished. At least that would give us a clue about what is happening. Blocking only creates confusion and difficult to track bugs.