Bushmills
Can't perform a real warm start which empties call stack but leaves dictionary intact
Therefore will errors and breaks (Ctrl-C) pile up new quit instances on top of those which got interrupted or error trapped.
Response of yoda to Ctrl-C can be set as preference in yoda.conv. This setting exists because of not having a clean warm start.
Current workaround: don't push Ctrl-C thousands of times.
Second best thing which I can currently do is a cold start instead, which will also reset dictionary to boot conditions (empty it, that is).
Not exactly the kind of response you wish to happen for a simple "word not found" typo.
status line show now the number of functions on call stack, which increases with each caught error or Ctrl-C. That number can be used to determine when the right time to exit and restart yoda may have arrived.
I usually don't let it grow beyond a low three digit number.