stack overflow through tasty takes forever

Created by: reiniervandijk

A stack overflow problem that occurs through interaction with Tasty, will generally take forever (status ...working until after a long while an error pops up in the lisp console). In contrast, on the REPL the user gets immediate feedback and may continue. Moreover, Tasty doesn't only hang forever but will also tend to consume all resources. As a consequence, Gendl becomes slow and doens't respond anymore. Only through (net.aserve:start :port XXXX) things get better, but don't really go back to natural state. It seems this behavior qualifies as another issue, because it happens quite often during developing (assuming error-free coding is a utopia). Can't these types of errors be caught in a leaner way, similar to what happens in the REPL?