Skip to content
This repository was archived by the owner on Mar 8, 2025. It is now read-only.

Conversation

JayPeet
Copy link

@JayPeet JayPeet commented Nov 19, 2021

Dispose was not called on the UnityWebRequest, which in newer versions of unity causes a memory leak.

disposeUploadHandlerOnDispose defaults to true, so it will also implicitly dispose that class.
This is backwards compatible to unity 2018, when the UnityWebRequest class was introduced, as it has always implement IDisposable (see: https://github.com/Unity-Technologies/UnityCsReference/blob/2018.1/Modules/UnityWebRequest/Public/UnityWebRequest.bindings.cs)

…ble with unity to when UnityWebRequest was introduced (as it has always implemented IDisposable, but no one ever seemed to call it :( )
@JayPeet
Copy link
Author

JayPeet commented Nov 19, 2021

Actually. I don't think this fully fixes the issue. Investigating

False alarm, I was seeing errors relating to it from previous runs of the plugin.

@JayPeet
Copy link
Author

JayPeet commented Nov 21, 2021

Actually, this sometimes still has the issue.

I'll look into it some more

@vanBassum
Copy link

Is this going to be merged? I would love to see this bug fixed.

@JayPeet
Copy link
Author

JayPeet commented Jun 6, 2022

I would love to, but it ended up not fully fixing the issue. I haven't had time to come back and resolve it :(

@maxtyson123
Copy link

I can confirm that on my machine this fixed the problem. It also wouldn't allow me to build before when I had the bug.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants