I just looked through upstream's bug tracker[1] to see if they had any updates on this issue, but I can't even find any mention of this issue, I sometimes doubt people remember to fix bugs unless they are filed in a bug tracker, so I've done so.[2]
Has anyone tried backporting the memory fixes that have been put into svn to see if that will solve this problem? Micah 1. http://bugs.bitlbee.org/ctrlproxy/report/1 2. http://bugs.bitlbee.org/ctrlproxy/ticket/35 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
