WASM Crash 1.1.2

[Hartley]

Hello!

I recently uninstalled the A350 and reinstalled when I heard about the 1.1.2 update to give her another shot. I had already cleared out the WASM folder prior to the reinstall. This was a clean install of the Inibuilds A350 and its first flight. I do not run any third party scenery at all, only what comes stock with Standard MSFS 2024. I landed at KLAX after coming from LFPG. While taxiing off the runway, the simulator froze. The plane would not move, and all gauges were stuck and the console reported a WASM crash. Pictures are attached. I attempted to do a .bin autosave but it would not save the airplane post-wasm crash. My last autosave prior to the wasm crash has been uploaded though. The second picture indicates a ground speed of 31 kts but the airplane was physically frozen and would not move. 

Simulator:  MFS2024

Aircraft: A350-900

Navdata Method: Navigraph
i7-13900k
RTX 4070
RAM 32GB

1753281701.bin

[Hartley]

Same thing just happened this time KLAX to RJTT. Same exact issue, as soon as I landed and taxiied off of runway 22 in RJTT, wasm crashed. The good part about these crashes is at least I'm able to file the flight report with my VA before the crash finishes . Again, couldn't create an autosave so I used one already created and uploaded that instead. I've also attached the console picture. Again, you'll see it says 39 kts for ground speed but the aircraft is completely frozen and locked up. Also WASM folder was completely cleared from above when this occurred the second time. 

EDIT: I swapped from using Navigraph Navdata to Sim Default nav data when this wasm crash occurred also. Not sure if that's important. 

1753296856.bin

Edited July 23 by Hartley