GNU bug report logs - #16344
24.3; xml-parse-region stuck on specific input, uses lots of memory

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Christopher Wellons <wellons <at> nullprogram.com>
Subject: bug#16344: closed (Re: bug#16344: 24.3; xml-parse-region stuck on
 specific input, uses lots of memory)
Date: Wed, 02 Mar 2016 18:12:03 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#16344: 24.3; xml-parse-region stuck on specific input, uses lots of memory

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 16344 <at> debbugs.gnu.org.

-- 
16344: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16344
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ulf Jasper <ulf.jasper <at> web.de>
To: Christopher Wellons <wellons <at> nullprogram.com>
Cc: 16344 <at> debbugs.gnu.org, 16344-done <at> debbugs.gnu.org
Subject: Re: bug#16344: 24.3;
 xml-parse-region stuck on specific input, uses lots of memory
Date: Wed, 02 Mar 2016 19:11:03 +0100

Fixed in branch emacs-25.

xml-parser will throw an error now.

[Message part 3 (message/rfc822, inline)]

From: Christopher Wellons <wellons <at> nullprogram.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.3; xml-parse-region stuck on specific input, uses lots of memory
Date: Sat, 04 Jan 2014 18:39:30 -0500

The function `xml-parse-region' is never returning from parsing this
specific input. It's saturing a CPU core while using huge quantities of
memory. Fortunately it can be aborted with C-g.

    (with-temp-buffer
      (insert "<!----><x>< /x>")
      (xml-parse-region))

The trigger is a comment followed by at least one opening tag followed
by a stray less-than character. This is not valid XML due to that extra
space in the closing tag, but I'm expecting `xml-parse-region' to signal
an error in the case of invalid input rather than lock up Emacs.

Just for the sake of context, this issue was initially discovered here:

https://github.com/skeeto/elfeed/issues/17

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.