malformed gntp messages have a tendancy to lock up regrowl, and for the offending application, also seem to put it in a deadlock. Particular instance... kfdm/irssi-growl and Growl::GNTP in Perl seems to be sending some kind of zero length message to the GNTP server before the actual message... the "easy" way to deal with this is to ignore zero-length data. I'm not sure if this is the elegant or "correct" solution