GNU bug report logs - #65445
29.1; Android emacs: False memory full condition, due to Java exception (?)

Previous Next

Full log

View this message in rfc822 format

From: Johan Widén <j.e.widen <at> gmail.com>
To: Po Lu <luangruo <at> yahoo.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 65445 <at> debbugs.gnu.org
Subject: bug#65445: 29.1; Android emacs: False memory full condition, due to Java exception (?)
Date: Tue, 22 Aug 2023 09:09:10 +0200

[Message part 1 (text/plain, inline)]

I now ran
  adb logcat -d | grep ...
and got the enclosed log lines, which seems to be from today, not from
the time of my bug report.
But it is for emacs.

Den tis 22 aug. 2023 kl 08:51 skrev Po Lu <luangruo <at> yahoo.com>:
>
> Johan Widén <j.e.widen <at> gmail.com> writes:
>
> > I used emacs swiper to search for "out of memory" but found nothing.
> > This was in the dumpstate*.txt file fetched by
> >   adb bugreport org.gnu.emacs
>
> Perhaps the log buffer has been rotated past the point of the error.
> Also, I believe adb bugreport only includes log messages after a crash:
> since Emacs is capable of recovering from these faux ``out of memory''
> errors, the message printed may not appear within generated bug reports.
>
> How about:
>
>   (adb) logcat | grep -A10 "Possible out of memory"
>
> ?



-- 
Johan Widén, tel: +46705367346
Risvägen 5 A, 192 73 Sollentuna, SWEDEN

[logcat.txt (text/plain, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.