From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.188.165 with SMTP id gb5cs389710vdc; Sun, 1 May 2011 11:17:42 -0700 (PDT) Received: by 10.52.165.136 with SMTP id yy8mr9902250vdb.194.1304273861944; Sun, 01 May 2011 11:17:41 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id t15si6469582vcr.98.2011.05.01.11.17.41; Sun, 01 May 2011 11:17:41 -0700 (PDT) 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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id BED82177994C; Sun, 1 May 2011 14:17:41 -0400 (EDT) Received: from mail-vw0-f50.google.com (mail-vw0-f50.google.com [209.85.212.50]) by rubyforge.org (Postfix) with ESMTP id 168801858367 for ; Sun, 1 May 2011 13:25:35 -0400 (EDT) Received: by vws14 with SMTP id 14so5180340vws.23 for ; Sun, 01 May 2011 10:25:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=mtz6QkcqliupijAfKxU0T9hDm8qHS7VMxjgM5+vOQRU=; b=NQEufF8gEpT16/rOwpBNqtx60ZPxKJp/b9TGzIKVPDqphymYA3gQe1uESx7uzQa/NJ nArSSxqHw8TbiA10divDPTw242N2lhK9aKw+lv2B4cROhm+9pHoQtiqWB040fk8f3HTS zUb+l3UW00GpAnN9wdqjqm2uo9OGkuq1bzSBw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=i4mw7zsxA1VQxBknlZMtj4w0RtUTOG8RxkJhhmeozGp6PpVD4jT3WSZelkOIUgIm56 wCKmSYVZZ9g8dC4ZWmjILi9H2gadYCuNsSVZ3MEZrd/+jDVwhuJXHK7wk3O2gQROl4QD 9g5Zpzgj1a9i583+yxJerZ50zsRvm+yDVZYjc= MIME-Version: 1.0 Received: by 10.52.186.69 with SMTP id fi5mr6786836vdc.205.1304270735436; Sun, 01 May 2011 10:25:35 -0700 (PDT) Received: by 10.52.110.65 with HTTP; Sun, 1 May 2011 10:25:28 -0700 (PDT) In-Reply-To: <1304265892-sup-7165@alpha> References: <1304265892-sup-7165@alpha> Date: Sun, 1 May 2011 18:25:28 +0100 Message-ID: From: Hamish D To: Felix Glaser Cc: sup-talk Subject: Re: [sup-talk] sup crashes while opening a big email thread 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org > Haven't had any trouble with sup until one of my email threads grew up to > almost 200 emails, right now the thread holds 202 mails. Whenever I try to > open the thread sup crashes, error log is attached as tar.gz. The simplest way to solve this would be to increase your stack limit a little: http://dalibornasevic.com/posts/5-ruby-stack-level-too-deep-systemstackerror Hamish _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk