Search Issue Tracker

By Design

Votes

7

Found in

2019.1.0a10

2019.1.0f2

2019.2.0a1

2019.3.0a1

Issue ID

1163092

Regression

Yes

[WebGL] Uncaught abort(-1) error in browser when running a built project which uses libassimp library

WebGL

-

How to reproduce:
1. Open the originally attached project 'New Unity Project.zip'
2. Build for WebGL (include "TriLib/TriLIb/Samples/Scenes/Scene1 - Asset Loader" scene)
3. Run the built project

Expected results: Project runs in the browser
Actual results: Errors regarding unresolved symbols in the browser console while loading

Reproducible with: 2019.1.13f1, 2019.2.0f1, 2019.3.0a11
Not reproducible with: 2017.4.30f1, 2018.4.5f1, 2019.1.0a9

Notes:
- Read about the library on https://github.com/google/filament/tree/master/third_party/libassimp

  1. Resolution Note (2020.1.X):

    The linking issue occurs because .bc files distributed in a "TriLib - Model Loader Package" have been compiled with a different version of Emscripten. Starting from Emscripten 1.38.10 type "size_t" changed from "unsigned int" to "unsigned long", which results in different mangled function names. The issue should be resolved by recompiling the package .bc files with the same version of Emscripten as used in the the target version of Unity.

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.