Random Godot 4.4 crash

Godot Version

4.4 beta 1

Question

OK. I have been having a Godot crash ever since I started using the 4.4 branch. There is a specific scenario where this (sometimes) happens. I want to know if any other C# projects are having this issue. When running my game and clicking the game window close button to exit, rather than stopping the run via Godot, the game window takes a few seconds to close and then Godot completely crashes, and I lose my Windows 11 desktop background. It only happens with Godot and only sometimes, maybe 25% of the times I follow this workflow for stopping my run. Has anyone else had this happen???
Faulting application name: Godot_v4.4-beta1_mono_win64.exe, version: 4.4.0.0, time stamp: 0x6789025d
Faulting module name: ntdll.dll, version: 10.0.26100.2454, time stamp: 0x7cb6b6a8
Exception code: 0xc0000374
Fault offset: 0x00000000000881f5
Faulting process id: 0x6054
Faulting application start time: 0x1DB69D0E0209AF8
Faulting application path: I:\Godot_v4.4-beta1_mono_win64\Godot_v4.4-beta1_mono_win64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: b6668f3a-ae84-491b-8072-ed1d930af7b2
Faulting package full name:
Faulting package-relative application ID:
A Windows exception with “Exception code: 0xc0000374” typically indicates a heap corruption error within the application, meaning there’s a problem with how memory is being managed, potentially due to a memory leak or invalid memory access within the program’s code.

Is this happening to anyone else using the Godot 4.4 branch?

While engine maintainers try their best to ensure that each preview snapshot and release candidate is stable, this is by definition a pre-release piece of software. Be sure to make frequent backups, or use a version control system such as Git, to preserve your projects in case of corruption or data loss.

As a tester, we encourage you to open bug reports if you experience issues with this release. Please check the existing issues on GitHub first, using the search function with relevant keywords, to ensure that the bug you experience is not already known.

In particular, any change that would cause a regression in your projects is very important to report (e.g. if something that worked fine in previous 4.x releases, but no longer works in this snapshot).

1 Like