Uncaught RangeError: Array buffer allocation failed

Hi I managed to get it to pack for HTML5. When I run Chrome or Nightly the bar completes but then it shows the error “Uncaught RangeError: Array buffer allocation failed” and it keeps compiling.I had increased the HEAP size in the project settings > HTML5

also in HTMLEngine.ini and still nothing changes

How can I fix this?

When I try to launch it within the program on Nightly or Chrome it says “Unable to connet” on the browser without any errors on the output log

This is exactly what it shows

This is the other error. This one shows up after I packaged and I run it through a local server on Firefox Nightly.

I had increased the HEAP size in the project settings > HTML5

also in HTMLEngine.ini and still nothing changes

Attached is my loglink text

How big of a heap did you try? Does it still do this with a 2GB heap size?

Unreal won’t let me change the heap side to more than 4096. I did try 2000mb on unreal and still same error Also, in the output log error towards the end it shows python.exe file size is 294mb may cause error in browsers.

I got the starter packaged to work in the browsers. But my project won’t work. How do I decrease the size of the package?

I also have compressed cooked content selected. If its not ticket the game exceeds 800mb

Please see attached for browser log

The maximum heap size you can try is 2048MB - 16MB = 2032MB. Browsers currently don’t support allocating anything larger than that.

If you are running on a 32-bit browser, a HEAP size of 512MB or 768MB is about the maximum that is possible.

In the current version of UE4 the amount of assets you have on disk contributes to this limit, so reducing the number of assets on disk can help here. In a later UE4 version I believe this should no longer be the case.

With upcoming WebAssembly spec, these types of errors should hopefully be avoided in the future: A WebAssembly Milestone: Experimental Support in Multiple Browsers - Mozilla Hacks - the Web developer blog, though unfortunately that feature is not quite yet out of the door in browsers.