From: Christian Tanzer via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65843@debbugs.gnu.org
Subject: bug#65843: 28.2; Too many iconified frames in .emacs.desktop -> crash (macOS)
Date: Sat, 9 Sep 2023 18:36:07 +0100 [thread overview]
Message-ID: <9E832564-CE62-4F99-960B-6058A0873084@gg32.com> (raw)
In-Reply-To: <83h6o3thpi.fsf@gnu.org>
On 09.09.2023, at 17:49, Eli Zaretskii <eliz@gnu.org> wrote:
>
>
>>
>> Date: Sat, 09 Sep 2023 16:35:56 -0000
>> From: Christian Tanzer via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> In Emacs 28 and Emacs 29, desktop-load crashes when there are too many
>> iconified frames in the .emacs.desktop file.
>>
>> The two attached .emacs.desktop files show the smallest test case that
>> I could come up with:
>>
>> - .emacs.desktop.works with 3 non-iconified and 4 iconified frames
>> loads without problem in Emacs 28
>>
>> + desktop-load of this file crashes in Emacs 29.1
>>
>> + a .emacs.desktop with 3 non-iconified and 3 iconified frames works
>> in Emacs 29.1
>>
>> - .emacs.desktop.crashes with 3 non-iconified and 5 iconified frames
>> leads to a crash in Emacs 28 (see attached problem report generated
>> by macOS)
>>
>> - I tried .emacs.desktop with up to 17 non-iconified frames in Emacs
>> 28 without problems
>>
>> - Up to Emacs 27, I've never seen a problem with desktop-load crashing
>
> Thanks, can you run Emacs 29 under a debugger and show a backtrace
> when it crashes?
Unfortunately, I don’t have a C development environment setup on my little MacBook (and haven’t used gdb for more than 20 years besides).
next prev parent reply other threads:[~2023-09-09 17:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 16:35 bug#65843: 28.2; Too many iconified frames in .emacs.desktop -> crash (macOS) Christian Tanzer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09 16:49 ` Eli Zaretskii
2023-09-09 17:36 ` Christian Tanzer via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-09 17:39 ` Eli Zaretskii
2023-09-10 14:11 ` Christian Tanzer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 14:27 ` Eli Zaretskii
2023-09-10 15:07 ` Gerd Möllmann
2023-09-10 15:37 ` Christian Tanzer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 16:04 ` Gerd Möllmann
2023-09-09 19:53 ` Alan Third
2023-09-10 4:20 ` Gerd Möllmann
2023-09-10 14:59 ` Christian Tanzer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 15:37 ` Gerd Möllmann
2023-09-10 15:40 ` Christian Tanzer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 17:09 ` Gerd Möllmann
2023-09-10 17:38 ` Gerd Möllmann
2023-09-10 17:09 ` Alan Third
2023-09-10 18:40 ` Gerd Möllmann
2023-09-10 19:54 ` Alan Third
2023-09-11 4:07 ` Gerd Möllmann
2023-09-11 4:50 ` Gerd Möllmann
2023-09-11 7:55 ` Christian Tanzer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 8:06 ` Gerd Möllmann
2023-09-11 16:25 ` Alan Third
2023-09-11 17:16 ` Christian Tanzer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 18:26 ` Alan Third
2023-09-12 17:43 ` Christian Tanzer via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9E832564-CE62-4F99-960B-6058A0873084@gg32.com \
--to=bug-gnu-emacs@gnu.org \
--cc=65843@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tanzer@gg32.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).