Subject: bug#16344: closed (Re: bug#16344: 24.3; xml-parse-region stuck on specific input, uses lots of memory)

From: [email-masked] (GNU bug Tracking System)
Date: Wed, 02 Mar 2016 18:12:03 +0000

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 [email-masked].

-- 
16344: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16344
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#16344: 24.3; xml-parse-region stuck on specific input, uses lots of memory
From: Ulf Jasper <[email-masked]>
To: Christopher Wellons <[email-masked]>
Cc: [email-masked], [email-masked]
Date: Wed, 02 Mar 2016 19:11:03 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

Fixed in branch emacs-25.

xml-parser will throw an error now.

Subject: 24.3; xml-parse-region stuck on specific input, uses lots of memory
From: Christopher Wellons <[email-masked]>
To: [email-masked]
Date: Sat, 04 Jan 2014 18:39:30 -0500
List-Id: <debbugs-submit.debbugs.gnu.org>

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