Do something silly like place a GEngine->AddOnScreenDebugMessage(…); inside a loop going over 60k verts inside the tick function and the editor will hang after several million messages (maybe it runs out of keys?).
I have to do an end process or Stop Debugging in VS to end the editor which has become unresponsive.
Maybe have some kind of check or handling of excessive messages? 
Hey Burnrate-
Attempting to do loop through anything 60,000 times each frame is going to cause performance issues. On top of this, draw calls and debug messages are already expensive processes and making this many calls is going to have an impact on performance. You can instead try writing a message to the logs rather than using a debug message on screen. I would also suggest only making this call when necessary rather than on tick as well as making your loop size smaller if possible to reduce how much information is being processed at once which will help performance.
Cheers
Absolutely I didn’t mean to have the message in there at all! I was just thinking it would be good if there was a way to debug when this happens as opposed to the editor just freezing. Thanks!