Hi,

before I try to reproduce this exactly I wondered if the following is a known issue with Pharo5. If I am in the debugger and try to step over a message send and that would generate a DNU, Pharo starts taking 99% cpu time. If I use CMD+./CTRL+. to interrupt it doesn't really work either. I get it to repaint the screen once and see a lot of message boxes with errors but the system remains unresponsive.

Is that known?