From: Po Lu 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: yang.yingchao@qq.com, bjorn.bidar@thaodan.de, 70352@debbugs.gnu.org
Subject: bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory
Date: Sun, 14 Apr 2024 14:28:33 +0800 [thread overview]
Message-ID: <87sezo1mr2.fsf@yahoo.com> (raw)
In-Reply-To: <86frvoo5pi.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 14 Apr 2024 08:48:09 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I thought the question I asked was for you to answer, not for the OP:
> how come the OP bumped into a problem that (AFAIU) could only happen
> when using code that is not in the Emacs Git repository?
Because the OP, presumably, built code that I published elsewhere (and,
I had hoped, discreetly enough to avoid the attention of casual Emacs
users).
next prev parent reply other threads:[~2024-04-14 6:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 10:56 bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory Yang Yingchao via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-13 1:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-13 7:15 ` Eli Zaretskii
2024-04-13 10:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-13 12:02 ` Eli Zaretskii
2024-04-14 0:11 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87sezozttr.fsf@>
2024-04-14 0:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-14 5:48 ` Eli Zaretskii
2024-04-14 6:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-04-14 7:31 ` Eli Zaretskii
[not found] ` <699acc927ca7decaaac0d06a59c80426bb9ae3059c3eebd7cced56cb021310bf@mu.id>
[not found] ` <871q7argry.fsf@qq.com>
2024-04-15 1:36 ` bug#70352: Fwd: " Yang Yingchao via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <db6105b7ec2a3d0db0d1741e43bea07e1ca0a8e2e7f360933771f524e9266d13@mu.id>
2024-04-15 1:58 ` Yang Yingchao via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87wmoz75g4.fsf@qq.com>
2024-04-17 7:30 ` Yang Yingchao via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-27 8:32 ` Eli Zaretskii
2024-04-29 8:45 ` Yang Yingchao via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-29 11:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-29 12:27 ` Yang Yingchao via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-09 7:35 ` Eli Zaretskii
2024-05-10 0:00 ` Yang Yingchao via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-10 6:34 ` Eli Zaretskii
2024-05-10 20:34 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-10 20:34 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87h6f5h0cw.fsf@>
2024-05-11 0:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-14 3:05 ` Björn Bidar 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=87sezo1mr2.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=70352@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=yang.yingchao@qq.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).