- Home /
Webplayer crashes on Chrome, but not on any other browser. Any way to avoid ?
Hello Community =) I am creating a webplayer that takes several assetbundles and instantiate them in a scene. The result of this is a high peak in memory allocation (I regulated the download so it takes up to 10 at a time and queue the others). When done, the webplayer takes between 600 and 800 Mo of memory, on firefox, ie, and safari.
However, Chrome has a very different behaviour, it actually crashes when the assets are being downloaded. Is there something specific with google chrome that would cause such thing ? Is the limit lower on this browser ?
Answer by Quantum2 · Jul 25, 2013 at 03:05 PM
Opposite to Firefox, Chrome loads external plugins into his own processes (Firefox creates a plugincontainer process), because of this, all regular Chrome limits apply and when it hits a certain percentage of the host system available RAM it kills the page to avoid further crashes and/or system instability. Try compiling as a NaCL native client
Your answer
Follow this Question
Related Questions
Reasonable heap alloc. per second and total ? 0 Answers
I need my meshes to use less memory 3 Answers
Optimize (Garbage Collection, Memory usage) 1 Answer
Should you use = null to free memory for variables declared in Start()? 3 Answers
Basic question about optimization (store variable vs accessing) 1 Answer