Error on Chrome Beta 54: fatal flex scanner internal error--end of buffer missed

Unity Engine
1

We’ve recently been getting this error on many of our WebGL builds when running them in the latest Chrome Beta build. ( 54.0.2840.16 beta-m (64-bit) )

Screenshot of the stack trace: Screenshot at 15:36:55.png - Imgur

Since it seems to include shader parsing, I checked what shaders we being included in the build. It’s not much: Screenshot at 15:37:40.png - Imgur

Right now we’re just going to warn users on the latest version of chrome, but if this issue gets into the main chrome version, we’ll be in a lot of trouble.

Any help?

2

First of all, it is probably a good idea to submit a bug report to Google to make them aware of such issues, so they can hold back on any breaking changes. https://bugs.chromium.org/p/chromium/issues/list

Once there is a bug link, we can also ping our contacts at Google to bring it to their attention.

In this case, it may well be a bug on our side as well, given that the error comes from our shader code, so I recommend filing a bug to Unity as well (with a repro project), and posting the case number here, so we can take a look.

3

It’s the same as this: UnityLoader.js:1 fatal flex scanner internal error--end of buffer missed - Unity Engine - Unity Discussions

It’s a chrome bug (fixed already in the dev branch), but I don’t know the actual changeset that fixed it. I’m getting nervous this will make it into stable…

4

So in this case, it is very important to let Google know about the importance of this. Please file bugs with Google.