Hi. I built the project using Unity 5.0.1.p2. Then i load it in Chrome and watched amount of the used RAM memory through a Windows->TaskManager->Processes.
When the project was completely loaded it used 800 MB (That is already strange, the project very small) after loading the second scene, amount of the used memory jumped up to 1-1.1 GB. And when I returned on the first scene, process still used 1-1.1GB. If I correctly understand - memory wasn’t cleared from the previous scene. I didn’t use “DontDestroyOnLoad” in the second scene.
Main Question:
Why memory wasn’t cleared and how to clear it? Second question:
Why so small project right after start already uses 800 megabytes? Third question:
How the scene (which AssetBundle weight is 3MB) with few GUIWindows can occupy 200-300 MB?
In FireFox situation is even worse, memory isn’t cleared even after reload the page. And then process takes even more memory. It is necessary to reboot a browser or wait about 5-10 minutes, then the browser will release memory.
P.S.
I can’t use the profiler because it is broken on Windows in Unity 5.0. And I can’t use Unity 5.1 because of an Error which I described here.
I have this exact problem with the latest patch on 5.1 ! I tried to build an empty project, does not work either …
In fact, the web player load the project (the scrollbar is full), but the project is never launched and the memory keep increasing and make my browser crash.
I’m having exactly the same issue, using Unity5 free (updated to the latest version today) would love to know if anyone has a solution as a client is asking for a WebGL build soonest. I’m still searching for a solution, so I’ll post a reply if/when I find one.
I have same issue. But Windows Chrome only. Mac Chrome is no problem.
Memory Spike occurs just been left for several minutes WebGL App on Windows Chrome.
Immediately after Chrome to crash .
This problem has occurred from Unity5.2.1f.
I am not sure this is the same problem initially reported in this thread, however, there is a known memory leak in Chrome which Google is working on right now. We’ll post more info in the forum as soon as we know more.
Hello! Sorry to bump such an old thread but I believe I’m experiencing this issue today on Windows 10 Chrome 32-bit. If you leave the WebGL application running for about 2 mins it freezes. Is that the memory leak issue you’re referring to Marco?
Yes, that’s the issue, which we implemented a workaround for. If you are still experiencing a memory leak with 5.3.x, then it might be a different problem and it might be a good idea to send us a bug report with a project so we can investigate.