Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Hello! Are you using the latest stable version (0.11.3)? This used to be a bug in past versions, but it should be fixed now.

Yep, i am indeed on v0.11.3

Hmm, this is very weird then. We'll take a closer look to see if we can replicate, however the good news is that version 1.0 will not have this issue for sure, as it is using Godot 4 instead of Godot 3. We will see if we can fix it for v0.11.4, otherwise you might have to wait until v1.0, sorry!

That's alright. Nice to hear it'll be fixed though. Thanks

Hey, just confirming that the crash no longer happens for me in v0.11.4. Thanks for fixing it!

That's awesome, glad to know the issue is resolved!

(2 edits)

Oh dear, looks like I celebrated too soon. It's crashing again, different error in the log this time.

WARNING: ObjectDB instances leaked at exit (run with --verbose for details).

   at: cleanup (core/object.cpp:2070) - ObjectDB instances leaked at exit (run with --verbose for details).

ERROR: Resources still in use at exit (run with --verbose for details).

   at: clear (core/resource.cpp:417) - Resources still in use at exit (run with --verbose for details).

ERROR: There are still MemoryPool allocs in use at exit!

   at: cleanup (core/pool_vector.cpp:63) - Condition "allocs_used > 0" is true.

This error message only showed up the first time it crashed, though. The succeeding crash logs are just empty. I suppose I'll just wait for v1.0?

Oh, that's a shame. Apologies for the trouble caused. The good news is that version 1.0 is almost ready and shouldn't take too long to come out, we will post a new devlog about its current status soon.