godot: .Net / Windows / Main Branch: Editor Sometimes Crashes in Random Spot non-dev build

Tested versions

Godot v4.3.dev.mono (fe01776f0)

System information

Godot v4.3.dev.mono (fe01776f0) - Windows 10.0.17763 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4060 Ti (NVIDIA; 31.0.15.4601) - AMD Ryzen 9 5900X 12-Core Processor (24 Threads)

Issue description

For mono + non-dev builds, Godot Editor sometimes may crash on startup, furthermore debugging breaks at this line: image

Clicking the Continue button will show the program paused on exception, which is image

The error code is STATUS_HEAP_CORRUPTION (A heap has been corrupted.).

Steps to reproduce

I am not sure if this is an OS-specific issue, but the repro is here:

  1. Clone the commit fe01776f0.
  2. Build the source with the mono module and debug symbols enabled according to the documentation.
  3. Launch the editor, select and open a project.
  4. Inspect the issue happens sometimes.

Minimal reproduction project (MRP)

N/A

Maybe fixed by #89861

About this issue

  • Original URL
  • State: closed
  • Created 3 months ago
  • Reactions: 1
  • Comments: 19 (16 by maintainers)

Commits related to this issue

Most upvoted comments

If nothing else the PR linked does seem to resolve the issue I was having with the crashes. Have you tried it if there’re some lingering issues on your end?

Just to be clear, I have the same issues and I’m on windows 11.

Can confirm. And it doesn’t happen with dev_build enabled.

I removed the code to load certificates at main.cpp, then the crash happened elsewhere.

image

image

If nothing else the PR linked does seem to resolve the issue I was having with the crashes. Have you tried it if there’re some lingering issues on your end?

Can confirm that #89861 has fixed the issue on my end as well.

@AThousandShips request: regression, topic:dotnet

Just went back and tested through all commits. It started happening with eccdf1a.

3cac010 is still working fine for me.

Assuming it’s the same problem, for me this is happening since way over a week already. Sometimes it works, but usually it doesn’t. I’m not sure when exactly this was introduced, as I’m only rebuilding every 5-10 days. The version I’m currently using is from end of February, which I stayed on because this problem appeared afterwards. Same problem on 2 different machines, Windows 10 and Windows 11. I’m only using Mono builds.

I made 4 builds, and tests them by opening an empty project individually:

  • [OK] Dev5 [89f70e98d209563abb4dbc1f8cd5d76c81eb7940]
  • [OK] Dev5 Mono [89f70e98d209563abb4dbc1f8cd5d76c81eb7940]
  • [OK] Main [fe01776f05b1787b28b4a270d53037a3c25f4ca2]
  • [Crash!] Main Mono [fe01776f05b1787b28b4a270d53037a3c25f4ca2]

That narrows the scope of the issue: image

I went through the history building and this is the first where it breaks for me: 77f6e35a8dc34a649f817a9c3e3c2d341fe98457. The one before: 8bfc257e63ee30b18438c3dc7bad3293c8c16b30 works for me just fine. I hope I did it alright, first time trying this in this IDE but so far that’s it from my side. (by just fine I mean I can launch a project into editor, I haven’t spent more time in it so don’t know if it would crash at some point later while working with the editor)

Is it the same on your side?

EDIT: Also I take back the comment about debug_symbols making it work, it still crashes on me unless I also enable the dev_build. This should probably also have the regression label.

If nothing else the PR linked does seem to resolve the issue I was having with the crashes. Have you tried it if there’re some lingering issues on your end?

Will check soon

Now I’m extra confused since my builds don’t seem consistent.

These are what I done for each version:

  • I moved every built file to a sub folder (as shown down below) before starting a new build.
  • I didn’t delete anything inside modules/mono before performing a build.
  • I did build with module_mono_enabled=yes argument.
  • I did use the built binaries to generate mono glues at the correct location.
  • I did ran build_assemblies.py and ensure the results are copied to the dest directory.

These are the builds I made:

[OK] Dev5 [89f70e98d209563abb4dbc1f8cd5d76c81eb7940] [OK] Dev5 Mono [89f70e98d209563abb4dbc1f8cd5d76c81eb7940]

[OK] Main-3 [691bd17df819d51e4a4ea2aa304bdd9857d49295] [Crash!] Main-3 [691bd17df819d51e4a4ea2aa304bdd9857d49295]

[OK] Main-2 [84bdc8d1b0f12c540257878297163698c83c2d0d] [Crash!] Main-2 [84bdc8d1b0f12c540257878297163698c83c2d0d]

[OK] Main-1 [68ad520da4365c866ceea42e0238b2ea24647289] [Crash!] Main-1 [68ad520da4365c866ceea42e0238b2ea24647289]

[OK] Main [fe01776f05b1787b28b4a270d53037a3c25f4ca2] [Crash!] Main Mono [fe01776f05b1787b28b4a270d53037a3c25f4ca2]

This made me rebuild the dev5 afterward:

[OK] Dev5 [89f70e98d209563abb4dbc1f8cd5d76c81eb7940] [Sometimes Crash] Dev5 Mono [89f70e98d209563abb4dbc1f8cd5d76c81eb7940]

And this is the order I followed when building these versions. image

I can confirm this on windows 11 with latest master too. it has been happening for about a week or so. The project selection works fine but when trying to open the project it starts opening it, loading something then crashes without loading the editor properly (no matter if it’s a new project or an olde one), although at some rare moments (I don’t know why, planets aligned or something?) I get into the editor and crash a bit later but that’s like 1% of tries.