v1.0.3 of the iniBuilds A350 Airliner for MSFS24 & MSFS20 has been released. This update contains various stability and crash fixes in the WASM code. Download and install the update via the iniManager.

As you can read this on the iniBuilds Topic Forum:

v1.0.3
Stability and crash fixes to WASM code.
____________________________________________________________

Thank you for your valuable bug reports; your feedback has been instrumental in helping us identify the key issues affecting your experience. 

What We Have Found
Community reports have helped identify the following root causes:
Timing Conflicts: The update rates between third party services and the A350’s systems sometimes don’t align, which can create issues.
Memory Management: Certain data exchanges may cause unexpected increases in memory usage, which might result in crashes.

Memory Allocation Issue (What’s Happening?)
Our A350’s avionics suite uses WASM (WebAssembly), a lightweight, secure programming environment. 

• WASM needs memory to run add-ons – This includes aircraft avionics, custom systems, and other third-party add-ons.
• This doesn’t mean your physical RAM – The problem isn’t about your computer running out of memory (like when you open too many programs).
• WASM uses virtual memory – It manages its own memory space separately inside the simulator. Even if your PC has plenty of RAM, WASM can still run into issues if it can’t allocate memory correctly.
• When allocation fails, crashes happen – If WASM tries to request memory but can’t get it properly, it can cause the simulator to crash or freeze.

This is why some add-ons might become unstable, even if your PC has more than enough memory. The issue is inside WASM’s own memory management system, not your computer’s physical RAM.

What We Are Doing to Fix the WASM Memory Issue
To improve stability and reduce crashes in Microsoft Flight Simulator (MSFS) caused by WASM memory allocation issues, we have made several changes:

Switched to Smart Pointers

• Instead of manually managing memory, we are using smart pointers.
• This helps prevent memory leaks and automatically frees memory when it’s no longer needed.

Avoiding Unnecessary Copy Constructors

• Copying large objects in memory can be inefficient and lead to excessive memory usage.
• We are reducing unnecessary copies, which means better performance and lower memory footprint in the WASM environment.

Adding Delays to Third-Party Data Requests

• Previously, we were requesting external data at 30 FPS (30 times per second), which was putting too much load on the WASM environment.
• Now, we limit these calls to once per second, significantly reducing the memory and processing overhead.

Expected Benefits
 Fewer crashes due to memory mismanagement.
 More efficient memory use in the WASM environment.
 Better performance and smoother experience.

If you are able to reliably reproduce this crash and are willing to help us, please do reach out to management@inibuilds.com or alert one of our Community team.

We apologise for some of the instability still present but are committed to resolving it ASAP.

iniBuilds Team