IDE debuggen und __Recovery?

[Kas Ob.]

Well, all what i see from this stack is
1) MadExcept may be unable handle exception (or to be more accurate,) can't stack tracing under low memory, unless it is failing to handle its own exceptions.
2) There is recursive calls and this is more dangerous then (1)
3) The stack is cut short, this is not all !, and you need more powerful tool to capture the stack on such thread, for that use WinDbg.