Bug 52677

Summary:	xmllint loops endlessly in processing some index.docbook
Product:	[Websites] docs.kde.org	Reporter:	Thomas Heuving <heuving>
Component:	ksgmltools	Assignee:	Docbook Team <kde-docbook>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Thomas Heuving 2003-01-06 20:13:27 UTC

Version:            (using KDE KDE 3.0.99)
Installed from:    Compiled From Sources
Compiler:          gcc 2.95.2 
OS:          Linux

In compiling kmailcool 1.6.1, kontact 0.1 and kde-i18n-es, I managed to freeze my computer. 
It was spectacular with kmailcool (less than two minutes and I had to turn him off), but also in the other packages are some files index.docbook (namely doc/kalarm/index.docbook in the kontact release) which put xmllint in an endless loop, in which more and more memory is used.
For testing purposes, I compiled kontact with kde3rc5 without problems, so it's a problem with the new xmllint.

Comment 1 Lauri Watts 2003-01-06 20:32:13 UTC

What version of libxml2 do you have?  
  
This sounds like  http://bugs.kde.org/show_bug.cgi?id=51023

Comment 2 Thomas Heuving 2003-01-06 21:52:28 UTC

Subject: Re:  xmllint loops endlessly in processing some index.docbook

Am Montag Januar 6 2003 20:32 schriebst du:

> ------- What version of libxml2 do you have?

libxml2.so.2.4.28

Was downloaded and compiled by konstruct, which I used to compile 
everything; and LD_LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib with
QTDIR=/usr/lib/qt3.1 and KDEDIR=/opt/kde3rc6
Could use a /usr/lib/libxml2.so.2.4.23, but konstruct is building the 
new version for a reason?

>
> This sounds like  http://bugs.kde.org/show_bug.cgi?id=51023

Don't think so, because there are no coredumps, just a xmllint which 
loops endlessly and eats all the memory.

Tsch

Comment 3 Lauri Watts 2003-01-06 22:13:25 UTC

Not all people had the coredumps, the endless looping is definitely the same bug.  
Upgrade to 2.4.29 or better, where it's fixed. 

*** This bug has been marked as a duplicate of 51023 ***