emacs leaks memory after upgrade to 29.3

drgibbon · 04-14-2024, 12:05 AM

But on my laptop with Slack 15.0 and Emacs 29.3 stock (didn't compile it myself), I get the crash when going into the package manager:

Code:

Fatal error 6: Aborted
Backtrace:
emacs[0x577bf3]
emacs[0x425b3e]
[...]
emacs[0x42e038]
/lib64/libc.so.6(__libc_start_main+0xcd)[0x7f7a5a17003d]
emacs[0x42e5ba]
[1]    8718 IOT instruction  emacs -nw -Q

I updated my build script on desktop quite a bit, so maybe this is something to do with the stock SlackBuild?

GazL · 04-14-2024, 03:45 AM

When I simplify the slackbuild down to a single build, rather than having it try and build emacs twice, I have no issues with the resultant emacs packages. Pat's builds in 15.0/patches just seem to be broken.

drgibbon · 04-14-2024, 07:15 AM

I did the same and made it only compile once (build is attached), no crashes.

Tonus · 04-14-2024, 07:58 AM

@GazL
@drgibbon

Does it work even for

Code:

emacs --daemon

?

drgibbon · 04-14-2024, 08:22 AM

Yes seems to work fine:

Code:

emacs --daemon
emacsclient -nw

Then F10, o, M.

Not crashing.

GazL · 04-14-2024, 10:55 AM

Same, no problems at all after doing my own build

Tonus · 04-14-2024, 12:32 PM

Thank you @drgibbon

Just did a mix of your Slackbuild and @Lockywolf 's and it work fine here.

Still on current so no native compilation here, and I kept the dual build though.

drgibbon · 04-14-2024, 06:42 PM

If you want native comp, you can just recompile your gcc from the stock SlackBuild with:

Code:

--enable-languages=ada,brig,c,c++,d,fortran,go,lto,objc,obj-c++,jit

and then recompile Emacs using my build script above. The two-step compile is not necessary by the way, you still get X11 and terminal Emacs with the single build.