Solved

viewer not loading: webgl memory allocation error

Something very weird going on. Might there be a misconfiguration in one of the servers or something along those lines. Why is it happening to just some and not all!

Firefox 56.0.0 (32-bit) works
Firefox 56.0.1 (64-bit) works

Whatever it is, the devs are devoting all their focus to fixing this as soon as possible.

Don't know if this helps. I've managed to get my firefox to replicate the error.

1. spectate a race (loads fine with no issues)
2. close viewer window
3. spectate another race
4. error

i can't watch race of yesterday. bug every time i try. maybe it's because i'm in a 32 bit system?
(sorry for my bad english)

https://docs.unity3d.com/Manual/webgl-memory.html

Dealing with memory issues

When you see an error related to memory in a Unity WebGL build, it is important to understand whether it is the browser which is failing to allocate memory or if the Unity WebGL runtime is failing to allocate a free block of memory within the pre-allocated block of the Unity heap. If the browser is failing to allocate memory, then it may help to try to reduce the size used by one or more of the memory areas above (for instance by reducing the size of the Unity heap). On the other hand, if the Unity runtime is failing to allocate a block inside the Unity heap, you may want to increase the size of that instead.

Unity will try to interpret error messages to tell which of the two it is (and provide suggestions on what to do). Since different browsers may report different messages, that is not always easy, however, and we may not be interpreting all of them. When you see a generic “Out of memory” error from the browser, it is likely to be an issue of the browser running out of memory (where you might want to use a smaller Unity heap). Also, you may sometimes see browsers simply crashing when loading Unity content without showing a human-parseable error message. This can have many reasons, but is frequently caused by JavaScript engines requiring too much memory to parse and optimize the generated code.

Large-Allocation Http Header

Your server can emit the Large-Allocation http header for your content. This tells supported browsers (currently only Firefox) about your memory needs, allowing them to spawn a new process with an unfragmented memory space, or to perform other housekeeping to make sure that the large allocation succeeds. This can solve issues where the browser runs out of memory when trying to allocate the Unity heap, especially on 32-bit browsers.

Hi I B, can you tell me what kind of error you got?

And can you inform me if the version of FireFox or Chrome you use is 32-bit or 64-bit?

It's the same as in the original post "The browser could not allocate enough memory for the webgl content etc "

Fairly sure it's 64bit version.

Okay. If you can confirm it for me you can click on this button at the top right of the screen in Chrome, click on Help, then About Chrome. If it says 64-bit after the version number please say so.



In Firefox the steps are the same but instead of Help, you see a question mark symbol and then can click About Firefox.

mine is 32bit

The browser or OS? If browser, which one?

Seems I may have been wrong, there's nothing indicating 64bit so presumably it's 32?

Firefox V43.0.1 build id 20151216175450

Just to clarify,

The first instance of the race viewer is running ok in Firefox, it's only when I close the viewing window and open another race that the error occurs.

In Opera V43.0.2442.1144 the viewer won't load at all.

Google Chrome "The browser could not allocate enough memory for the WebGL content. If you are the developer of this content, try allocating less memory to your WebGL build in the WebGL player settings." This would indicate it is a setting at the web development end and not the computer or browser.

Try Opera Version: 48.0.2685.39 (PGO) - Opera is up to date
Update stream: Stable

https://www.opera.com/computer
https://www.opera.com/computer/mac
https://www.opera.com/computer/linux

Yes, the Firefox build is presumably 32-bit when it doesn't display 64-bit. Okay, can you download the 64-bit versions of the browsers you use and load the race viewer in those 64-bit versions?

I really think I may be on to something here, I'm clenching my teeth.

OK, downloaded latest 64 bit versions of Opera and Firefox.

Both run the race viewer ok with no apparent problems.

(apart from the fact that it's totally screwed my browser extensions, I'm clenching my teeth but in a different way to you I suspect)

I think you should be able to get any extensions you use installed to your 64-bit browsers, otherwise it may be a hassle to switch between 32- and 64-bit (or maybe not depending on the situation). If it's mostly with extensions like an ad blocker, and you have custom items blocked on particular websites that you've specifically chosen to block, and need it over in the 64-bit browser's extension I can help with that.

Lastly, if you have any issues in the 64-bit browers, please let us know. Also let us know if your experience with the race viewer has improved in 64-bit browsers as time passes, such as if you are no longer experiencing any issues.

Any error messages that appear please copy their text and post it here.

To efficiently find a cause and to properly sweep for and isolate the race viewer problem, I'm closing this thread.

I B, if you would like to follow up with me regarding your extensions, you are welcome to PM me or create a new thread. (I'm curious to know if I can help you with whatever it is)

To all, if you are receiving error messages when loading the race viewer or unable to load the race viewer at all on PC, please go here to post about it.

If you are unable to load the race viewer in the app, please go here to post about it.