Background downloading exception using www.Dispose() method

Hi guys,

Anyone run into any issues using background downloading of AssetBundles using the Dispose() method? Here is what my developer had to say about it:

I have spent quite a lot of time investigating the issue but it seems there is a problem in Unity code. The issue is definitely related to background loading and specifically www.Dispose() method. It seems that the Dispose() method doesn’t really stop www object from downloading the content if it hasn’t been finished yet. If I create another www after disposing the first one then both www objects will be updated and the latest created will show progress of both objects one after another.

I am currently submitting a project as a bug report but if anyone has any workarounds, please let me know.
Thanks,
T

Schubkraft, Marcus T or Jonas are you able to comment on this?

I am not aware about any problem with www.Dispose(). We received your bug report and we will take a look at it,

thanks!
Marco

1 Like

Hi Marco, I have seen some activity on the Gdrive with this, can you update any further? Could you reproduce? Thanks,A

Hi,

sorry for the delay. Could you please let me know which version of Unity this bug is reproducible with ?

Hi Marco, it was 5.1.2f1
Thanks,
T

ok.

one more question, have you tried to reproduce with the latest 5.1.3 patch?

No not yet, shall I?

yes please, that will save us some time.

I’ll ask my developer to take a look & get back to you

Hi Marco, issue is still present w 5.1.3p1. I am also PMing you some links to builds in case they’re of use.

Any update on this Marco?
Thanks
T

Sorry for the delay. It might be a bug we recently fixed but we won’t know for sure until we get more information.
Do you get any callstack on the browser console ? Is it chrome/firefox-specific ?

A bug report with project and repro steps would be great.

Resubmitted a case under the old bug report, still using 5.1.3p1 (5.2 sounds like it still has issues)
(Case 734141)

Just a quick update to let you know we have not been able to reproduce the issue with the project you provided.

In 5.1.3p1? or in 5.2.x?

Both 5.1.3p1 and 5.1.4f1

Hi Marco, I PM’d you and bugs@unity3d.com a 3 minute screencast of the steps to create the issue, and the issue itself occurring. Maybe my previously provided steps weren’t good for reproducing.
Hope this helps