From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24899 invoked by alias); 12 Oct 2015 16:51:24 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 36846 Received: (qmail 25665 invoked from network); 12 Oct 2015 16:51:23 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM, T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=G2WJvAMcx8Tudnh1T8gttD65TDH6ta/tyrPh9mx3czI=; b=FYTjrTdj/Re3pbneZFh8f3lPbyJDDaqu4tk4qTD/mC5qJMkUWDP2es6TYUTM+LNo4v 2LPUdlDynerpoWeOlcj8AWnoMap90zhuwLQbV1Yk/2IkZdqCFh2TrGK4Y0t0+tePM+T7 f8GMEruwPQb29p0nigCxp/ta55TvhHej2AQyCKkZSEG4o4/UELVXW1pWf6bSuBmg7CeC JUn8Vn3F5yPEy4Vzl6H2rYw0GsYxokS3e/oznrOPsMai8Qpsuxzzb8H32tXPSC/qKOMJ i1fTV8cvcaJpCZEoPn27IaomE6T1qdRS4TScRzlcXlYwka1VNn2QbmzbViYGzfVLOpDe A96w== X-Received: by 10.112.157.99 with SMTP id wl3mr12749390lbb.98.1444668679186; Mon, 12 Oct 2015 09:51:19 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <151012070105.ZM15099@torch.brasslantern.com> References: <151010105849.ZM10144@torch.brasslantern.com> <151010170623.ZM16166@torch.brasslantern.com> <151010232045.ZM12931@torch.brasslantern.com> <151011091757.ZM27755@torch.brasslantern.com> <151011103121.ZM8814@torch.brasslantern.com> <151011142204.ZM9103@torch.brasslantern.com> <151012070105.ZM15099@torch.brasslantern.com> From: Sebastian Gniazdowski Date: Mon, 12 Oct 2015 18:50:59 +0200 Message-ID: Subject: Re: Slowdown around 5.0.5-dev-0 To: Bart Schaefer Cc: zsh-workers@zsh.org Content-Type: text/plain; charset=UTF-8 On 12 October 2015 at 16:01, Bart Schaefer wrote: > If you configure --enable-zsh-heap-debug you can edit mem.c to set a > value for the heap_debug_verbosity variable which will cause a LOT of > debugging messages to be printed to stderr. This may tell you where > it's spending time. Did that, set heap_debug_verbosity to 0x7f. When I issue a search, screen gets constantly outputted with messages about heap pop. One series started with: HEAP DEBUG: heap ff604f popped, old heap was ff51af. HEAP DEBUG: heap ff6050 popped, old heap was ff51b0. HEAP DEBUG: heap ff6051 popped, old heap was ff51b1. To then went through: HEAP DEBUG: heap ff5592 popped, old heap was 52dde. HEAP DEBUG: heap ff5593 popped, old heap was 52ddf. HEAP DEBUG: heap 50984 popped, old heap was 4fe96. HEAP DEBUG: heap 50985 popped, old heap was 4fea7. And ended at: HEAP DEBUG: heap 5145f popped, old heap was 50981. HEAP DEBUG: heap 51460 popped, old heap was 50982. HEAP DEBUG: heap 51461 popped, old heap was 50983. Set my terminal scroll back to "unlimited", repeated that. However scroll back buffer got cut off at some point. At top there was: HEAP DEBUG: heap fb5f19 popped, old heap was fb5079. HEAP DEBUG: heap fb5f1a popped, old heap was fb507a. ... Then: HEAP DEBUG: heap fb5466 popped, old heap was d35b. HEAP DEBUG: heap fb5467 popped, old heap was d35c. HEAP DEBUG: heap a41f popped, old heap was 9931. HEAP DEBUG: heap a420 popped, old heap was 9942. And at the end: HEAP DEBUG: heap aefb popped, old heap was a41d. HEAP DEBUG: heap aefc popped, old heap was a41e. HEAP DEBUG: heap 9931 popped, old heap was 98f8. HEAP DEBUG: heap 98f8 freed, new id is fb71a8. HEAP DEBUG: heap fb71a8 pushed, new id is fb71a9. HEAP DEBUG: heap fb71a9 popped, old heap was fb71a8. Maybe the numbers mean something? Best regards, Sebastian Gniazdowski