From: Noam Postavsky <npostavs@gmail.com>
To: Adam <adam.niederer@gmail.com>
Cc: 31771@debbugs.gnu.org
Subject: bug#31771: 26.1; Writing image file with emacs hangs entire system
Date: Sat, 09 Jun 2018 15:47:27 -0400 [thread overview]
Message-ID: <87y3fnzqr4.fsf@gmail.com> (raw)
In-Reply-To: <d77f49e7-3c4b-eb1e-3a12-d4dca6f93c92@gmail.com> (Adam's message of "Sat, 9 Jun 2018 13:53:09 -0400")
tags 31771 + unreproducible
quit
Adam <adam.niederer@gmail.com> writes:
> After following these commands, your emacs should freeze, and then your
> entire system should hang a few seconds later.
I couldn't reproduce this. No hang, and if I look closely, I can see
the one black pixel rendered correctly in the top left corner.
Is your whole system completely frozen, or is it perhaps just using so
much RAM that it goes into swap and starts thrashing and becomes very
slow? If the former, I guess it's some kind of graphics driver thing,
though it seems a bit funny that an image as simple as a single black
pixel could wreck it.
> My hunch: this is caused by emacs trying to render the image after it's
> saved. Unfortunately, this causes emacs and my system to hang, so I
> can't provide any core dumps. I'm using linux 4.16.13, mesa 18.1.1,
> libpng 1.6.34, and imagemagick 7.0.7.38
> Configured features:
> XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GSETTINGS NOTIFY
> ACL GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS
> GTK3 X11 MODULES THREADS LIBSYSTEMD LCMS2
Do you really have imagemagick 7? Or do maybe also have imagemagic 6?
As far as I know, the patch for Emacs to use v7 is not merged yet:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25967#41
next prev parent reply other threads:[~2018-06-09 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-09 17:53 bug#31771: 26.1; Writing image file with emacs hangs entire system Adam
2018-06-09 19:47 ` Noam Postavsky [this message]
2018-06-09 22:09 ` Adam
2018-06-10 2:53 ` Noam Postavsky
2018-06-10 17:53 ` Adam
2018-07-23 1:56 ` bug#31771: 26.1; [imagemagick] " Joerg Kulbartz
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=87y3fnzqr4.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=31771@debbugs.gnu.org \
--cc=adam.niederer@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 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).