Re: Tab bar tabs landed on master

[Eli Zaretskii]

> Date: Sat, 2 Nov 2019 00:13:10 +0100
> From: Ergus <address@hidden>
> Cc: Emacs developers <address@hidden>
> 
> I am trying the tabs in the master branch and with my config it works
> fine in tui. But for some reason in GUI, when I create a new tab, emacs
> freezes:

Can we please use the bug tracker for reporting and investigating
bugs?  This list is not the right place for that.

> In gdb the bt shows:
> 
> #0  0x000055addb2b837f in mark_object (arg=<optimized out>) at 
> ../../src/alloc.c:6583
> #1  0x000055addb2b8f0e in mark_vectorlike (header=0x7f98b16ae700) at 
> ../../src/alloc.c:6157
> #2  0x000055addb2b8373 in mark_object (arg=<optimized out>) at 
> ../../src/alloc.c:6581
> #3  0x000055addb2b8f0e in mark_vectorlike (header=0x7f98b16ae660) at 
> ../../src/alloc.c:6157
> #4  0x000055addb2b8373 in mark_object (arg=<optimized out>) at 
> ../../src/alloc.c:6581
> #5  0x000055addb2b8f0e in mark_vectorlike (header=0x7f98b16ab3f8) at 
> ../../src/alloc.c:6157

Are you saying that Emacs starts GC and never finishes it?  If you set
garbage-collection-messages non-nil, do you see the message announcing
GC displayed once or many times one after the other?

> I thought that this happened because I have this in the config:
> 
> ```
> (defun my/minibuffer-setup-hook ()
>    (setq gc-cons-threshold most-positive-fixnum))
> 
> (defun my/minibuffer-exit-hook ()
>    (setq gc-cons-threshold 800000)
>    (garbage-collect))
> 
> (add-hook 'minibuffer-setup-hook #'my/minibuffer-setup-hook)
> (add-hook 'minibuffer-exit-hook #'my/minibuffer-exit-hook)
> ```
> 
> But I commented it and it didn't change anything.

Do you have any other GC-related customizations?  They could be in
packages you load, not necessarily in your init files.  What are the
values of gc-cons-threshold and gc-cons-percentage after you comment
out the above parts?

> Do you have any idea about where to look to fix this?

Bisect your init file, if nothing else gives a clue.

And once again, please report this as a bug, and let's continue
discussion on the bug tracker.

Thanks.