Handle debug-level Tor log severity efficiently
Configure your Vidalia to listen to debug-level Tor logs, leave the message window open, and then do something active with your Tor. Vidalia will go nuts trying to keep up with displaying all the lines, resizing them, and whatever else it's trying to do. It's too inefficient handling each new line, and trying to do thousands of them at once just overwhelms it.
Why? What can we do to fix or mitigate? If we can't fix, maybe we should make it more discouraged to click the 'debug' button?
While I'm at it, why does Vidalia set up its own log files from the message window, when it could configure Tor so Tor does the logging?