From: Brad Town via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 11081@debbugs.gnu.org, "Eli Zaretskii" <eliz@gnu.org>,
"Jan Djärv" <jan.h.d@swipnet.se>
Subject: bug#11081: 24.0.94; "emacsclient --create-frame" occasionally crashes daemon or causes daemon to hang
Date: Sat, 4 Dec 2021 12:50:09 -0800 [thread overview]
Message-ID: <CAEkDjn2ryw4n_49GwQ7ahHPPjcbU=8A=4ct7SfBM9p5Q0k9dsQ@mail.gmail.com> (raw)
In-Reply-To: <87h7bo3zq8.fsf_-_@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
I haven't used this functionality in a long time. I think it's reasonable
to close this issue.
On Sat, Dec 4, 2021, 12:02 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Jan Djärv <jan.h.d@swipnet.se> writes:
>
> > No, the new frame that is being created is not live when this code is
> > executed. The crash happens when emacsclient --create-frame is run,
> > not when exiting the frame. The f->terminal is indeed NULL, and
> > x_display_list is NULL.
>
> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
>
> Are you still seeing this issue in more recent Emacs versions? (I can't
> recall seeing any reports like this, at least.)
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
>
[-- Attachment #2: Type: text/html, Size: 1299 bytes --]
next prev parent reply other threads:[~2021-12-04 20:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 23:19 bug#11081: 24.0.94; "emacsclient --create-frame" occasionally crashes daemon or causes daemon to hang Brad Town
2012-03-24 12:01 ` Jan Djärv
2012-03-29 16:27 ` Brad Town
2012-03-31 17:16 ` Jan Djärv
2012-03-31 18:00 ` Eli Zaretskii
2012-04-01 9:33 ` Jan Djärv
2021-12-04 20:02 ` Lars Ingebrigtsen
2021-12-04 20:50 ` Brad Town via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-12-04 21:02 ` Lars Ingebrigtsen
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='CAEkDjn2ryw4n_49GwQ7ahHPPjcbU=8A=4ct7SfBM9p5Q0k9dsQ@mail.gmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=11081@debbugs.gnu.org \
--cc=brad@bradtown.com \
--cc=eliz@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=larsi@gnus.org \
/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).