Don't try to display the frame information in the backtrace when a !MemoryError occurred.
Trying to render the frame data usually triggers ''another'' !MemoryError exception, hiding the potentially interesting backtrace of the first one, like in #4081 and #6101.
