#18671 closed bug (invalid)

Double free at emacs 29.1 startup in graphics mode

Reported by: haikupr Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: - General Version: R1/beta4
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

emacs 29.1 as installed from haiku depot crash before it finish the evaluation of my .emacs file. This crash only occurs when emacs is started in graphics mode and when evaluating my .emacs file. emacs complete its startup when launched from a ssh connection, or from Terminal with the -nw or -q options. The exact same startup script under FreeBSD or Omnios does not cause these emacsen to crash.

This crashing behavior is quite old, I resolved myself to use emacs only over ssh but today I decided to report this bug because I think others may be affected or it may have a deep source. The crash reports did evolve over time, with the old c++ allocator, an explicit message mentioning a double free was produced; later it was obvious that (double?) freeing a font-related structure was involved; today the bug looks to be triggered during garbage collection.

I attach the latest crash report I have (older ones were not kept). I won't attach my .emacs and its dependencies because this is quite a large set (~6 MiB) and I'm not proud of the crud I accumulated in it over it 30 years of existence. I can mail it privately if required.

Attachments (1)

emacs-29.1-1417-debug-17-11-2023-18-25-44.report (24.2 KB ) - added by haikupr 13 months ago.
emacs crash report

Download all attachments as: .zip

Change History (3)

by haikupr, 13 months ago

emacs crash report

comment:1 by augiedoggie, 13 months ago

Normally crash reports for ported software would be submitted to the HaikuPorts issue tracker on github, assuming that it's not a problem with Haiku itself. In this case since Haiku is an officially supported target for Emacs then the bug should be reported to them.

comment:2 by waddlesplash, 13 months ago

Resolution: invalid
Status: newclosed

emacs is third-party software and its bugs are thus not tracked here.

Note: See TracTickets for help on using tickets.