Are there any other ways to discern the cause of a project window crash?

This is a READ-ONLY snapshot of the Godot Community Forums when TwistedTwigleg was the owner, which is hosted for archival reasons only. The current Godot Community Forums can be found here.

Some links may point to external websites, including the current Godot Community Forums. These websites are not associated with TwistedTwigleg.

Are there any other ways to discern the cause of a project window crash?

KnightNine

I've fixed all the reproducible errors that I've encountered in my extremely large project but now after my project is running for some amount of time, being able to otherwise run without issue, the window eventually just crashes abruptly (though maybe not exactly abruptly, seems to happen when something resource intensive is happening), and the log file doesn't show anything out of the ordinary. With no pattern in the log file to suggest that it is happening because of anything gdscript related what are my other options? Running the profiler on a project this resource intensive causes it to freeze whenever anything happens and eventually crash in the same manner.

My project has some significant stuttering issues right now, and I'm theorizing if there's maybe a risk of Godot crashing whenever there's a stutter/whenever something resource intensive happens, like when I add a bunch of nodes to the scene at once, regardless of whether there are any gdscript related issues or not.
I wasn't sure if it was a threading issue since the freeze can happen even when the threads in my project are idle, but I tested my project without threading and the same thing seems to happen eventually.

My other theory is that the cause is somehow related to the number of errors in my project since I have made a habit out of letting the engine discern whether a node exists because it returns null anyways and I can use the errors to figure out what assets I'm missing later in development.:
e.g.

#instead of checking with has_node(), i just see if it returns null or not (this also prints an error)
var audio_player = get_parent().get_node("AudioStreamPlayer3D")
if audio_player != null:
 	pass#do something

Also I do the same with using load()

I am also using the print() function an insane amount of times, maybe that could be the cause. 🤔

I could test exporting the project to see if it runs without crashing but it would be necessary to be able to run the entirety of my project with debugging enabled so that I can... debug.

Are there any ways of seeing maybe deeper causes of why my project is crashing or is it something engine related? Any insights and suggestions would be much appreciated.

cybereality

You can run the game on the command line (or the editor too) by launching it from the console. This gives more info sometimes than the log files.

However, I bet your problem is the print statements. There is a limited buffer for printing, it is probably large (in the thousands of lines) but still limited. Overflowing this could cause problems.

Really prints should only be used for quick debugging and then remove then when the issue is solved. You can setup some sort of logging to either save to a file or print to a window on the screen (sort of like the old Doom games or Half-Life). This is a better method if you want to have verbose printing used throughout the game.