bug#4993: 23.1; rmailmm.el mime decode crashes emacs

bug#4993: 23.1; rmailmm.el mime decode crashes emacs

[Walter Neumann]

Opening the mail file available at
http://math.columbia.edu/~neumann/bug with rmail and typing "v" to
view the message using rmail-mime crashes emacs: emacs starts using
100% cpu and becomes unresponsive. Tested on two systems, with and
without init files loaded.


In GNU Emacs 23.1.1 (i386-redhat-linux-gnu, GTK+ Version 2.16.6)
 of 2009-09-29 on x86-7.fedora.phx.redhat.com
Windowing system distributor `The X.Org Foundation', version 11.0.10603901
configured using `configure  '--build=i386-redhat-linux-gnu' '--host=i386-redhat-linux-gnu' '--target=i586-redhat-linux-gnu' '--program-prefix=' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include' '--libdir=/usr/lib' '--libexecdir=/usr/libexec' '--localstatedir=/var' '--sharedstatedir=/var/lib' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--with-dbus' '--with-gif' '--with-jpeg' '--with-png' '--with-rsvg' '--with-tiff' '--with-xft' '--with-xpm' '--with-x-toolkit=gtk' 'build_alias=i386-redhat-linux-gnu' 'host_alias=i386-redhat-linux-gnu' 'target_alias=i586-redhat-linux-gnu' 'CFLAGS=-DMAIL_USE_LOCKF -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-bu
 ffer-size=4 -m32 -march=i586 -mtune=generic -fasynchronous-unwind-tables''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_US.utf8
  value of $XMODIFIERS: nil
  locale-coding-system: utf-8-unix
  default-enable-multibyte-characters: t

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
<escape> x r e p o r t - e m a c s - b u g <return
>

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.

bug#4993: 23.1; rmailmm.el mime decode crashes emacs

[Glenn Morris]

Walter Neumann wrote:

> Opening the mail file available at
> http://math.columbia.edu/~neumann/bug with rmail and typing "v" to
> view the message using rmail-mime crashes emacs: emacs starts using
> 100% cpu and becomes unresponsive. Tested on two systems, with and
> without init files loaded.
[...]
> In GNU Emacs 23.1.1 (i386-redhat-linux-gnu, GTK+ Version 2.16.6)
>  of 2009-09-29 on x86-7.fedora.phx.redhat.com

I can't reproduce a "crash" in either 23.1 or the CVS trunk.
23.1 decodes the message in a reasonable time, but slightly incorrectly.
The trunk decodes it correctly, but very slowly (it can be interrupted
any time with C-g). Is this what you meant? If so, it is fixed now.

bug#4993: 23.1; rmailmm.el mime decode crashes emacs

[Walter Neumann]

Yes indeed, no crash: I misinterpreted "very slow" (over 15 minutes on my 
machine) and the fact that the emacs window was unkillable (I didn't think 
to try ctl-g). And CVS fixes it. Thanks.

--walter

On Sat, 21 Nov 2009, Glenn Morris wrote:

> Walter Neumann wrote:
>
>> Opening the mail file available at
>> http://math.columbia.edu/~neumann/bug with rmail and typing "v" to
>> view the message using rmail-mime crashes emacs: emacs starts using
>> 100% cpu and becomes unresponsive. Tested on two systems, with and
>> without init files loaded.
> [...]
>> In GNU Emacs 23.1.1 (i386-redhat-linux-gnu, GTK+ Version 2.16.6)
>>  of 2009-09-29 on x86-7.fedora.phx.redhat.com
>
> I can't reproduce a "crash" in either 23.1 or the CVS trunk.
> 23.1 decodes the message in a reasonable time, but slightly incorrectly.
> The trunk decodes it correctly, but very slowly (it can be interrupted
> any time with C-g). Is this what you meant? If so, it is fixed now.
>