From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-31382-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 25137 invoked by alias); 7 May 2013 21:56:04 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 31382
Received: (qmail 23129 invoked from network); 7 May 2013 21:55:58 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE,
	RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2
Received-SPF: none (ns1.primenet.com.au: domain at grayvines.com does not designate permitted sender hosts)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:x-received:in-reply-to:references:date:message-id
         :subject:from:to:cc:content-type:x-gm-message-state;
        bh=q2XkHN2mGbQYnn/Z79vndPzhyKgeUoIieN2nxq4PImM=;
        b=gpjKq4Ig2sIti03y7BWa7/+E0YpcN3HFYje96IlY2uQuWjO5b5I2kBkuq1Drb+BA51
         eHPF+WLRbzSjMUyGONA5joSmo6IbSkwptcsaLGwqYvBrgh9gMQ05nwXizEfmAtJ91Mm7
         6opzID21BdoNY83mYorGG5xYPWv4Uvrl7NbA2qDl+0a5EsZydBVnthgw92Ho8rt4MLFq
         IwmLblBmwi7lvyZ/qnAaX4+XWauO4K6cn5/o3E6qc3+3niDnuo4Fj/8hP1NLEbkbqZxe
         a8KkDzheblfoNT0EAgBxjkclz7ttkuecM1QbtYkXgnaUsZV/EkdjnFaTuJFK+tL7AVYM
         G7NQ==
MIME-Version: 1.0
X-Received: by 10.112.161.38 with SMTP id xp6mr1831058lbb.32.1367963749141;
 Tue, 07 May 2013 14:55:49 -0700 (PDT)
In-Reply-To: <CAH+w=7ZtqhyX5SgpOUz-i7RHAMY_YeiTBPR+pWQjquNT4Jfk6w@mail.gmail.com>
References: <CABJQSkk0f4e3p3YWjjEhr0qr31Etht2jsp3m_qFdEnDkpyzZ9A@mail.gmail.com>
	<CAH+w=7ZtqhyX5SgpOUz-i7RHAMY_YeiTBPR+pWQjquNT4Jfk6w@mail.gmail.com>
Date: Tue, 7 May 2013 17:55:48 -0400
Message-ID: <CABJQSkkgzcYeDHUrF0HiqAF0eiXp8h1jvmzNHWZi0_Bv_GixxQ@mail.gmail.com>
Subject: Re: Crashing shell on 5.0.2 OSX, logs attached
From: Julian Berman <julian@grayvines.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: multipart/alternative; boundary=001a11c264fe55636604dc27e143
X-Gm-Message-State: ALoCoQlUzALsHUktejN8+ww/N8jcjKPNDwjojh//ii4tyx2+MF8mmfW8l1r3ehimt/580prEHxTO

--001a11c264fe55636604dc27e143
Content-Type: text/plain; charset=ISO-8859-1

Looks like you're right, disabling syntax-highlighting did it, guess I
should have tried that considering syntax highlighter's warnings, though
I've used it since around when it came out and haven't really experienced
anything interesting until now.

Thanks for the pointer.

Julian
On May 7, 2013 5:22 PM, "Bart Schaefer" <schaefer@brasslantern.com> wrote:

> These both appear to be memory-management related, but otherwise
> aren't connected, so both are probably a symptom of an actual bug
> that's elsewhere.  I strongly suspect something that is triggered by
> syntax highlighting, either via _fuzzy-match-accept-line or from
> somewhere inside zsh-syntax-highlighting.  Try removing one or both of
> those from your .zshrc and see if you can still reproduce the problem.
>

--001a11c264fe55636604dc27e143--