Search Issue Tracker

Fixed in 2.0.0-preview.13

Votes

6

Found in [Package]

2018.4

2019.3

2019.3.3f1

2020.1

2020.2

Issue ID

1225060

Regression

No

[WebGL] [SVG] "Runtime error: float unrepresentable in integer range" is thrown on WebGL builds when using Vector Graphics

Package: Vector Graphics

-

Reproduction steps:
1. Open the user's attached project ("VectorGraphicsBugReport.zip")
2. Open the repro scene ("SampleScene")
3. Enter Play Mode and notice the "UnityEngine.Vector2[]" log
4. Exit Play Mode
5. Make a WebGL (development) build and run it

Expected result: Build launches without errors
Actual result: Build crashes with "Runtime error: float unrepresentable in integer range" errors

Reproducible with: 2018.4.19f1, 2019.3.6f1, 2020.1.0b2, 2020.2.0a4
Couldn't test with: 2017.4 (SVG package is not supported)
Reproducible with package versions: 1.0.0-preview.19, 1.0.0-preview.34, 2.0.0-preview.6, 2.0.0-preview.12

Tested with: Chrome (80.0.3987.149), Firefox (74.0), Edge (80.0.361.69)

Notes:
1. On 2018.4, 2019.3 streams, the issue only reproduces on development builds
2. On 2020.1, 2020.2 streams, the issue reproduces with both development and release builds
3. Additionally, this error is also thrown: "An abnormal situation has occurred: the PlayerLoop internal function has been called recursively. Please contact Customer Support with a sample project so that we can reproduce the problem and troubleshoot it."

Comments (15)

  1. Braza

    Jul 05, 2020 18:45

    Facing this on 2019.4.1f1

  2. peach_blitz

    May 07, 2020 21:30

    I found a temporary fix - although emscripten arguments aren't exposed in Project Settings, they can be modified in your project's ProjectSettings.asset file. In this file, if your "webGLEmscriptenArgs" field is empty, emscripten is not using clamp mode, which can result in the aforementioned error.

    Modifying the field to the following worked for me in solving the issue:
    webGLEmscriptenArgs: -s "BINARYEN_TRAP_MODE='clamp'"

    I hope this helps expedite the fix. More info here: https://emscripten.org/docs/compiling/WebAssembly.html#trapping.

  3. FdenUijl

    May 07, 2020 11:20

    I also have this issue (Unity 2018.4.22f1)

  4. peach_blitz

    May 06, 2020 23:40

    I am also having this issue using Unity 2020.1.0b7.3356

  5. pablo_leban

    May 01, 2020 06:51

    Im currently having this issue as well (using Unity 2020.2.0a7.826)

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.