WASM modules not unloading when aborting flight loading

Version: 1.3.23.0

Frequency: Consistently

Severity: Low

Context: FBW A320/A380 with 2024 wasm modules

Bug description:
It seems like wasm system modules (with the 2024 approach in the systems.cfg) keep running on the world map/main menu when aborting the load into a flight. So basically pressing escape before spawning. When loading a new flight, the “kill” callback and “initialize” callbacks are executed, but that is causing some problems in the systems.

The issue does not occur once the flight is loaded. Upon exiting, everything is unloaded properly. Loading a new flight then also causes no issues.

When switching planes, the wasms also get unloaded properly.

“Old” gauges also do not suffer from this, they are being unloaded even if I abort the loading of the flight.

Repro steps:

I can provide a package if needed. Basically it is using a plane with systems wasm (using the 2024 approach) and aborting the loading of a flight before the spawn happens.

Attachments:

Can provide package if necessary.

Hello,

Can you provide us with a repro package please ?
See 3) Provide Private Content.

Regards,
Boris

Hi Boris,

you can use the following package:

It’s the “fbw.wasm” module that stays loaded when the “flight loading” is aborted on the world map screen.
The issue does not appear once in flight and returning to the main menu from there.

Best,
Sascha

Hello,

Thank you,
I was able to reproduce the issue and have therefore logged a bug in our backlog.

Regards,
Boris

3 Likes