From: "Johan Widén" <j.e.widen@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Po Lu <luangruo@yahoo.com>,
65445-done@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#65445: 29.1; Android emacs: False memory full condition, due to Java exception (?)
Date: Sat, 2 Sep 2023 20:56:17 +0200 [thread overview]
Message-ID: <CACxzjrv=rEtEM4j1Kb73j-B86ZrfyXGHR0_q-g4r4SJRcg3zSg@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmmAHBUe9rBTrXSXi6w9s0EOLa=_TR5drRLGLgcHN0GHFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 259 bytes --]
Glad to hear it!
On Sat, Sep 2, 2023, 20:52 Stefan Kangas <stefankangas@gmail.com> wrote:
> Johan Widén <j.e.widen@gmail.com> writes:
>
> > Yes, it seems to be fixed. I can no longer provoke the bug.
>
> Thanks, I'm therefore closing this bug.
>
[-- Attachment #2: Type: text/html, Size: 617 bytes --]
prev parent reply other threads:[~2023-09-02 18:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 20:46 bug#65445: 29.1; Android emacs: False memory full condition, due to Java exception (?) Johan Widén
2023-08-21 23:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-22 2:27 ` Eli Zaretskii
2023-08-22 2:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-22 5:21 ` Johan Widén
2023-08-22 5:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-22 5:52 ` Johan Widén
2023-08-22 6:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-22 7:09 ` Johan Widén
2023-08-22 7:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-02 16:30 ` Stefan Kangas
2023-09-02 17:21 ` Johan Widén
2023-09-02 18:52 ` Stefan Kangas
2023-09-02 18:56 ` Johan Widén [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACxzjrv=rEtEM4j1Kb73j-B86ZrfyXGHR0_q-g4r4SJRcg3zSg@mail.gmail.com' \
--to=j.e.widen@gmail.com \
--cc=65445-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=stefankangas@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.