public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: A workaround against Emacs crash when displaying images
Date: Thu, 07 Mar 2019 15:55:00 -0000	[thread overview]
Message-ID: <e65d27db-ccfd-38ee-7372-f67dd5259125@cornell.edu> (raw)
In-Reply-To: <b4mr2bjo7qp.fsf@jpl.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 958 bytes --]

On 3/6/2019 7:20 PM, Katsumi Yamaoka wrote:
> Hi,
> 
> I found a workaround for Emacs from crashing that always happens
> when displaying images in an html article using Gnus.  That is:
> 
> export MAGICK_THREAD_LIMIT=1
> 
> According to the Google search someone said the crash arises due
> to a bug in ImageMagick incorporating OpenMP.  I don't know what
> it means at all, though. ;-)
> 
> Regards,
> 
> uname -a
> CYGWIN_NT-10.0 localhost 3.0.2(0.338/5/3) 2019-03-05 18:57 x86_64 Cygwin

Is this a new issue with cygwin-3.0.x?  If so, it might be related to the memory 
leak that was recently discovered (and fixed in the latest snapshot):

   http://www.cygwin.org/ml/cygwin/2019-03/msg00122.html

Ken
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

  reply	other threads:[~2019-03-07 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07  0:20 Katsumi Yamaoka
2019-03-07 15:55 ` Ken Brown [this message]
2019-03-07 23:36   ` Katsumi Yamaoka
2019-03-08  4:36     ` Katsumi Yamaoka
2019-03-08 12:05       ` Corinna Vinschen
2019-03-10 23:12         ` Katsumi Yamaoka

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=e65d27db-ccfd-38ee-7372-f67dd5259125@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.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. 
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).