From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: james@jojojames.com
Cc: 57267@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#57267: 28.1; emacs crashes when loading too many images
Date: Sun, 21 Aug 2022 07:30:57 +0200 [thread overview]
Message-ID: <m2zgfy6u3y.fsf@Mini.fritz.box> (raw)
In-Reply-To: <FF5001F4-856C-4DC7-9F38-4CCB9B3A4C06@jojojames.com> (james@jojojames.com's message of "Sat, 20 Aug 2022 12:23:58 -0400")
james@jojojames.com writes:
>
>> Could it be that one or more jpegs of yours is invalid in some way?
> Maybe you could check this with the 'jpeginfo' utitlity. I've never
> used it myself, because I don't have a use for it, but from what I read,
> it might be able to detect at least some error cases. Maybe it's worth
> trying.
>
> Do you think that would lead to a crash every time? My crashes are
> very inconsistent.
I can't really answer that question because, as a starter, I don't even
know what AppleVPA is doing when it crashes, and there's no way to find
out, AFAIK. In general, with multi-threading, ASLR, and whatnot, things
tend to not behave consistently quite frequently, at least in my
experience.
I'd personally give jpeginfo a try. It's cheap. Just 'brew install'
it.
>> Another idea might be to try and install an external jpeg library
> (libjpeg I presume), and configure Emacs to use it. Alas, this doesn't
> seem to work on my M1 Mac, but maybe it does on your x86_64 system.
>
> Can you point me to some documentation for that?
I can't find documentation for this. I guess I only "know" about this
because I added it in 1998, according to the ChangeLog, which must be a
lie :-).
Anyways. On my system, I just did 'brew install libjpeg' and then
'./configure'. The file config.log showed that configure was trying to
use libjpeg, but didn't like it for some reason I don't remember.
BTW, Homebrew also has other jpeg libs ('brew search jpeg' and so on),
but I didn't try them all. As I mentioned, I don't do much with images
myself.
Maybe it's also worth asking an help-gnu-emacs, if this doesn't work.
Or someone reading this knows more about this topic.
next prev parent reply other threads:[~2022-08-21 5:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 0:38 bug#57267: 28.1; emacs crashes when loading too many images james
2022-08-18 6:30 ` Eli Zaretskii
2022-08-18 18:49 ` james
2022-08-18 19:03 ` Eli Zaretskii
2022-08-18 20:14 ` james
2022-08-19 5:55 ` Eli Zaretskii
2022-08-19 6:01 ` james
2022-08-19 7:18 ` Gerd Möllmann
2022-08-19 7:22 ` Gerd Möllmann
2022-08-19 14:18 ` james
2022-08-20 6:34 ` Gerd Möllmann
2022-08-20 16:23 ` james
2022-08-20 16:29 ` james
2022-08-21 5:42 ` Gerd Möllmann
2022-08-21 5:30 ` Gerd Möllmann [this message]
2022-08-21 21:21 ` james
2022-08-23 5:09 ` Gerd Möllmann
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=m2zgfy6u3y.fsf@Mini.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=57267@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=james@jojojames.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).