From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs455798agc; Mon, 2 Nov 2009 03:53:47 -0800 (PST) Received: by 10.224.24.136 with SMTP id v8mr2800250qab.79.1257162827185; Mon, 02 Nov 2009 03:53:47 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 35si7336898qyk.28.2009.11.02.03.53.47; Mon, 02 Nov 2009 03:53:47 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 6696E167830B; Mon, 2 Nov 2009 06:53:46 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 50C5C16782B1 for ; Mon, 2 Nov 2009 06:53:40 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1N4vTf-0006cb-KD; Mon, 02 Nov 2009 03:53:40 -0800 From: William Morgan To: Steven Walter In-reply-to: References: <1256939095-sup-4201@masanjin.net> <1257087035-sup-2014@masanjin.net> Date: Mon, 02 Nov 2009 03:53:39 -0800 Message-Id: <1257162594-sup-7077@masanjin.net> User-Agent: Sup/git Cc: Sup-talk mailing list Subject: Re: [sup-talk] Recovering a busted ferret db? X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org [cc'ing list] Reformatted excerpts from Steven Walter's message of 2009-11-01: > Hooray, that worked. There is an email with an exceptionally long > recipient list with the tag in question, and I received it around the > time I first noticed the bad behavior in sup. The Cc: field is 6878 > bytes long, containing 281 email addresses. Weird, because I can call split_on_commas on a string that's that size, with that many commas, in a few milliseconds. Must be something strange about that particular string that's causing the worst-case behavior. I'm going to apply the patch, but with a bigger limit. -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk