Search Issue Tracker

Fixed in Unity 2019.1

Votes

8

Found in

2017.4.2f2

Issue ID

1032870

Regression

No

[WebGL] Player continues to run after webgl-content is removed from DOM

WebGL

-

-

Priority: 4Not yet prioritized for a release

-

Severity: 3Secondary functionality broken

Reproduction steps:
1. Open the attached project.
2. Build and run it for WebGL.
3. Press the "remove webgl-content from document" button.
4. Open a web console.

Actual behavior:
- Player will still run and the error message will be shown - "Screen position out of view frustum".

Reproduced with:
2018.3.0a1, 2018.2.0b3, 2018.1.0f2, 2017.4.2f2, 2017.2.2p4

Tested with:
Firefox 59.0.2

Note:
The error message doesn't show up in 2017.1.3p4

Response avatar

Resolution Note:

It is now possible to quit via either C# or JS: - C#: call Application.Quit() - JS: call unityInstance.Quit()

Comments (1)

  1. Eb5c28d1cb07ffb8e2bea41c295d7784?d=mm

    MFKJ

    Mar 19, 2019 05:31

    Even after exit the application properly with above function, i am getting aw snap crash in chrome while wasm:out of memory error in mozilla.

    failed to asynchronously prepare wasm: out of memory UnityLoader.js:4:9417
    printErr http://localhost/HS_Test_DataCachingDisable_EmptyProject/Build/UnityLoader.js:4
    instantiateArrayBuffer blob:http://localhost/610a0d84-d049-4128-8a17-80b140369ecf:2
    out of memory UnityLoader.js:4:9417
    printErr http://localhost/HS_Test_DataCachingDisable_EmptyProject/Build/UnityLoader.js:4
    onAbort http://localhost/HS_Test_DataCachingDisable_EmptyProject/Build/UnityLoader.js:4
    abort blob:http://localhost/610a0d84-d049-4128-8a17-80b140369ecf:2
    instantiateArrayBuffer blob:http://localhost/610a0d84-d049-4128-8a17-80b140369ecf:2

    The error produce after several refresh/reload on chrome and firefox.

All about bugs

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