title: Over populating Logcat causes windows to freeze, until hard reboot is performed
body: <p>The title speak for itself, but I would add some pointers I've noticed along the way.
  I would like anyone which also experience the end result while developing for Android to try to reproduce this and see if this scenario is really the case, and if someone have a solution, that would make me very happy :), it is extremely frustrating that I need to hard reboot my computer while developing...</p>
  
  <p>The crash happens when Logcat is over populated. By over populated I mean that from a point in time, if you would leave a device connected in debug mode for a while, and you would look at the Logcat view, it would display only the new 'delta' lines added to the log in the past short interval of about 2 sec.</p>
  
  <p>If you would pay attention, while the Logcat is over populated the device which is been debugged, response slowly to user interaction(this can be your indication, that the Logcat is over populated while testing your application), and perform other actions ridiculously slow. </p>
  
  <p>If you would leave the Device connected and more logs would be added, there is a short interval 5-10 sec, where Eclipse starts to behave weird, and after that, there is nothing you can do, Windows 7 freezes and only hard reboot allows you to get back to work.</p>
  
  <p>I can reproduce this every time, if I would just leave a device connected in debug mode with an application running.</p>
  
  <p>I've Googled this, and came up with nothing. I assume that if me and my colleagues encounter this(we have the same Eclipse setup), then other should also experience this, so before posting a bug, I would like to confirm this...</p>
  
  <p>details:</p>
  
  <p>Windows 7</p>
  
  <p>Eclipse 3.6</p>
  
  <p>ADT 10.0.0.v201102162101-104271 (Latest for today)</p>
  
  <p>Thanks,</p>
  
  <p>Adam.</p>