Search Unity

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

Discussion in 'Web' started by Sprakle, Sep 9, 2016.

  1. Sprakle

    Sprakle

    Joined:
    Jun 8, 2013
    Posts:
    31
    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: http://i.imgur.com/lzWNIY1.png

    Since it seems to include shader parsing, I checked what shaders we being included in the build. It's not much: http://i.imgur.com/wwrF9AB.png

    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?
     
    Sprakle, Sep 9, 2016
    #1

  2. jonas-echterhoff

    jonas-echterhoff

    Unity Technologies

    Joined:
    Aug 18, 2005
    Posts:
    1,666
    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.
     
    jonas-echterhoff, Sep 12, 2016
    #2

  3. kognito1

    kognito1

    Joined:
    Apr 7, 2015
    Posts:
    331
    kognito1, Sep 12, 2016
    #3

  4. jonas-echterhoff

    jonas-echterhoff

    Unity Technologies

    Joined:
    Aug 18, 2005
    Posts:
    1,666
    jonas-echterhoff, Sep 12, 2016
    #4