all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo <sdl.web@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 9079@debbugs.gnu.org
Subject: bug#9079: integer overflow etc. issues (e.g., image crashes Emacs)
Date: Thu, 14 Jul 2011 20:54:48 +0800	[thread overview]
Message-ID: <m1vcv5t42v.fsf@gmail.com> (raw)
In-Reply-To: <4E1EA0FB.5070903@cs.ucla.edu> (Paul Eggert's message of "Thu, 14 Jul 2011 00:55:39 -0700")

On 2011-07-14 15:55 +0800, Paul Eggert wrote:
> Here's an example bug.  Take the attached file 46341x46341.png.gz,
> uncompress it with 'gunzip', start up Emacs under X Windows, execute
> (setq max-image-size 50000), and then visit the file 46341x46341.png.
> If you're lucky Emacs will thrash around for quite some time and then
> dump core.  If you're unlucky Emacs's internal data structures will be
> silently corrupted.

A long time ago I found that emacs-w3m tend to crash emacs when loading
images. So I have the following in my setup.

;;; Don't open any images in w3m; it causes crashes. This function was
;;; originally defined in w3m-ems.
(defalias 'w3m-image-type-available-p 'ignore)

Leo





  parent reply	other threads:[~2011-07-14 12:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14  7:55 bug#9079: integer overflow etc. issues (e.g., image crashes Emacs) Paul Eggert
2011-07-14  8:22 ` Andreas Schwab
2011-07-14 16:15   ` Paul Eggert
2011-07-14  8:47 ` Eli Zaretskii
2011-07-14 16:23   ` Paul Eggert
2011-07-14 17:48     ` Eli Zaretskii
2011-07-14 22:02   ` Paul Eggert
2011-07-15  5:46     ` Eli Zaretskii
2011-07-15  7:22       ` Paul Eggert
2011-07-14 12:54 ` Leo [this message]
     [not found] ` <handler.9079.B.13106301884386.ack@debbugs.gnu.org>
2011-07-28  0:49   ` bug#9079: Acknowledgement (integer overflow etc. issues (e.g., image crashes Emacs)) Paul Eggert

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=m1vcv5t42v.fsf@gmail.com \
    --to=sdl.web@gmail.com \
    --cc=9079@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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.