TeaVMOptimizationLevel.ADVANCED and AssetManager.finishLoading() break release build

[Hyperion2400]

I have encountered a problem with the newest gdx-liftoff version 1.14.2 and Java 21. I'm not sure where the problem lies.

If the following conditions are met

• TeaCompiler optimization level is either TeaVMOptimizationLevel.ADVANCED or TeaVMOptimizationLevel.FULL
• AssetManager's finishLoading() is called

I get the following errors in the browser when loading the TeaVM build:

Uncaught ReferenceError: BSr is not defined
    at app.js:3137:398
    at app.js:2:228
    at app.js:2:274
Uncaught (in promise) ReferenceError: main is not defined
    at start ((index):28:17)

The LibGDX loading screen doesn't even appear. Everything works fine when using TeaVMOptimizationLevel.SIMPLE.

I have created a minimal reproducible example: https://github.com/Hyperion2400/TeaVMBug

[tommyettinger]

Yes! I have noticed this too, but only when building JS. I'm glad you were able to find a stable reproducible case; I hadn't been able to do that. In the short term, you can try targeting WASM by uncommenting the line in TeaVMBuilder:

.setWebAssembly(true) /* Uncomment this line to use WASM output instead of JavaScript output. */

I haven't been able to reproduce the bug with WASM, only JS targets. WASM certainly seems much faster in some cases than JS, but I am not sure if the WASM-GC variant it uses works on mobile Safari yet. That's the only reason I still will target JS at all, so if/when mobile safari supports the WASM that TeaVM produces, I can switch that commented line to uncommented by default.

I'll try to bring this up with @xpenatan , the author of gdx-teavm, to try to rule out any TeaVM bug before I potentially mention it to TeaVM proper. It might be something that AssetManager is doing that's not ideal for TeaVM when generating JS.

[tommyettinger]

So when disabling obfuscation, it narrows down "BSr" and shows that it's really some kind of TemporalAction.

Uncaught ReferenceError: cbgssa_TemporalAction__init_1 is not defined
    at app.js:84944:120
    at app.js:10:9
    at app.js:12:2
index.html?_ijt=t8ig2rs0cerpcqhl9gveq5c7d1&_ij_reload=RELOAD_ON_SAVE:28 Uncaught (in promise) ReferenceError: main is not defined
    at start (index.html?_ijt=t8ig2rs0cerpcqhl9gveq5c7d1&_ij_reload=RELOAD_ON_SAVE:28:17)

I'm still using ADVANCED optimization here, but not obfuscating. I'm not sure if this will help figure out the problem, but it's a start.

[xpenatan]

Hey,

Can you try the -SNAPSHOT version? The snapshot release uses TeaVM 0.15.0, and in my testing it appears to be fixed.

The only breaking change is that TeaCompiler has been renamed to TeaBuilder.

[Hyperion2400]

Hey,

Can you try the -SNAPSHOT version? The snapshot release uses TeaVM 0.15.0, and in my testing it appears to be fixed.

The only breaking change is that TeaCompiler has been renamed to TeaBuilder.

Yep, that seems to fix it. 👍

[tommyettinger]

Hooray! I'll update gdx-teavm when there's a release.