Fresh heap memory WebGL Unity on Chrome

Question

I had some problem when run Webgl on Chrome:

Memory still on ram when I close my Webgl game:
- Before run my game: 1.00G ram
- While run my game: 1.9G ram
- After close my game: 1.8G ram
- Run game again: 2.5G ram => Array buffer allocation failed
Memory fragmented while refresh page many time => not enough memory for consecutive block (heap) => Array buffer allocation failed

How can I fresh heap after close my WebGL game?

Any suggestion to fix that issues?

Hey did you solve this issue? – Muhammad Faizan Khan Mar 18 '19 at 14:15 — Muhammad Faizan Khan, Mar 18 '19 at 14:15

score 0 · Answer 1 · answered Sep 08 '16 at 06:49

0

This may not be Unity's fault. Usually when tabs are closed in Chrome, it takes time for the memory to the freed. Sometimes 4 to 10 minutes. This is what I noticed from the Task Manger. It doesn't free up memory right away. Sometimes, you even have to close the current Chrome browser for closed tab memory to be freed. I can't tell if this is a bug or feature. Maybe, Calling GC.Collect() might help.

You should put the code below in your script to see if that would help.

void OnDisable()
{
    GC.Collect();
    GC.WaitForPendingFinalizers();
}

answered Sep 08 '16 at 06:49

Programmer

121,791
22
236
328

Thanks for your answer, but it's not working on my issue, memory still on Ram. – Hoàng Đức Sep 09 '16 at 04:44
What Unity version is this? – Programmer Sep 09 '16 at 07:28
1

GC.Collect doesn't work on webgl. The only time garbage collection works on webgl is when you load a scene – nexx Jun 28 '17 at 11:50
@nexx once i red in unity forum that gc.collect do work but don't make any impact. – Muhammad Faizan Khan Mar 18 '19 at 12:04
is there any latest available about this problem? – Muhammad Faizan Khan Mar 18 '19 at 12:05

score 0 · Answer 2 · answered Mar 18 '19 at 14:30

According to Unity Forums In Unity 2019.1, there is proper method to Quit and cleanup the WebGL player:

C#: call Application.Quit()
JS: call unityInstance.Quit(callback)

You can use JS asynchrous function like this:

unityInstance.Quit(function() {
    console.log("done!");
});
unityInstance = null;

If you are using Application.Quit of C# then you can provide its callback in JS like this:

UnityLoader.instantiate("unityContainer", "%UNITY_WEBGL_BUILD_URL%", {onProgress: UnityProgress,
    Module:{
      onQuit : function(){
        console.log("unity has quit");
      }
    }
});

My Observation/Caution: According to my current observation, it is not freeing the memory and the second is that currently unity 2019 is in beta stage. If anyone use this quit feature please let me know that it is working or not.

Fresh heap memory WebGL Unity on Chrome

2 Answers2