Re: Slowdown around 5.0.5-dev-0

[Sebastian Gniazdowski <sgniazdowski@gmail.com>]

On 12 October 2015 at 16:01, Bart Schaefer <schaefer@brasslantern.com> 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