This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
On some pages (some examples pointed from http://lists.w3.org/Archives/Public/www-validator/2010Jun/0013.html), the Validator takes a lot of CPU for a very long time (and usually times out in the on-line version). The problem seems to be linked to the latest version (1.70) of XML::libXML ; a ticket was reported back in April 2010: https://rt.cpan.org/Public/Bug/Display.html?id=56671 Villes analysis of the problem has more details and ideas: http://lists.w3.org/Archives/Public/public-qa-dev/2010Jun/0002.html Doesn't seem like there is any easy way around that problem, thgouh
Candidate fix in CVS: http://dev.w3.org/cvsweb/validator/httpd/cgi-bin/check.diff?r1=1.776&r2=1.777
The mentioned fix as well as http://dvcs.w3.org/hg/markup-validator/rev/d32ff17ac5c8 have been in production since release 1.1 and have as far as I can tell worked around the problem satisfactorily so I'll mark this as resolved. Further, XML::LibXML development has been resuscitated recently and the root cause is supposedly fixed in >= 1.77.