We know the source of this bug, however, getting it fixed was going to
take much longer than we had for 1.4 due to the sandboxing deadline,
and 1.4 has a number of fixes and improvements that needed to ship.
The best stop gap for now is to quit or force quit growl and relaunch
it when it starts doing it. We got into this situation by not being
careful enough with the design and implementation of the previous
networking stack, so we are going to take the time we need to make
sure its right this time. Growl 2.0 is the intended target for the
new networking stack.