Interpreter stack limit exceeded, and other stack crashes in 0.8.0

Description

This came up from testing one of my games on Interpreter which uses the Input library. Input does a lot of jumping around and calls a lot of recursive functions while setting itself up, namely __input_initialize and __input_global are the main culprits. During execution, the interpreter crashes with "interpreter stack limit exceeded".

I made a test project to isolate the issue and have a few findings: Note that these numbers seem to vary to some extent in the range of +/-20, for GMRT's Interpreter, at least.

GMRT

Interpreter

Recursing ~280 times causes a crash without an error message.
Calling debug_get_callstack returns an empty array every time, but each call takes longer based on the depth of the callstack.
throw/show_error freezes for an extreme period proportional to the callstack length.
Thrown errors after ~100 callstack depth are not reported on crash.

Native

Recursing ~4000 times crashes without an error message.
Calling debug_get_callstack returns the callstack array correctly, but as with the interpreter, calls get substantially slower over time.
Thrown errors any point before the ~4000 threshold are reported correctly.
Crashing with a long callstack does not cause any freeze.

Current Runtime (for reference)

VM

Recursing can be done to any depth without error.
Thrown errors at extreme (I haven't narrowed this down) callstack length are not reported, runtime crashes without error pop-up with "Stack Overflow detected!!! exiting..."
Callstacks longer than ~75 messages are cut off in the error.
Callstacks at length of exactly 2237 no longer report errors on crash, and the runtime crashes silently.

YYC

Recursing ~4200 times crashes without an error message.
Apparently I need to report a bug for YYC because its callstacks are straight up missing from the Code Error box as of 2024.600.

Expected Change

No response

Steps To Reproduce

A) Input

This is the first way I found this behaviour, which lead onto B. Import Input into a new project. The version present in my project was 6.1.4, although I tested on the latest 6.3.1 and encountered the exact same issue.

Compile with the Interpreter, and you will encounter the original "interpreter stack limit exceeded" message. This message, in my testing, was hit, depending on the version, at:

In 6.1.4, on the second call to __input_initialize, made by a recursive call to __input_global(). The moment the function was called, it would crash. I tried querying its _initialized value using __input_initialize[$ "_initialized"] == true, and if that was true, would not call it again. This just moved the error to a bit later.
In 6.3.1, in the first call to __input_initialize, either a show_error call, or if that call was no-oped to continue further, a seemingly random nested function call in ___input_config_verbs would cause a crash. Inspecting where this happened seemed to move it around, which I somewhat expected given it was a crash with the callstack being too long.

B) `crash()`

To further test, I made a very quick and dirty test function in a new project:

function crash(depth = 0) {

    show_debug_message($"Callstack depth: {depth}");

    if (depth < 1000) {
        crash(depth + 1);
    }

    throw "kaboom";

}

crash();

Changing that < 1000 value to others was all I used to get the other test information. I also added {debug_get_callstack()} in the debug message for testing that, but it is not present as shown here.

Test Project: GMRT-Interpreter-Stack-Limit-Reached.zip

How reliably can you recreate this issue using your steps above?

None

Which version of GameMaker are you reporting this issue for?

Beta (Please put the exact version number in your Description)

Which platform(s) are you seeing the problem on?

Windows

Compiler Log File

[ ] I have attached my compiler log in a text file

Sample .yyz File

[X] I have attached a small sample project

YoYoGames / GameMaker-Bugs