This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Validating the DOM Level2 CR apparently buggars up some component of the Validator during processing, resulting in an "Internal Server Error" returned to the browser. cf. original report from Karl Dubost <http://lists.w3.org/Archives/Public/www-validator/2002Dec/0140.html>.
Hmmm. It looks like for DOM2.html we grow our resident size by a factor of 100:1 due to the huge ESIS generated and inefficient handling. Either we need more RAM on v.w3.org or we need to implement mmap() when the ESIS exceedes some (configurable?) limit. First step is to profile to see why a 12.5MB ESIS grows to over a 100MB resident size. :-(
Retarget 0.7.0.
Retarget to "1.0"; this wants S:P:O to implement.
We no longer have ESIS in HEAD but once (if) we do DOM-based stuff we might have similar problems. Perhaps we should just enforce a maximum file size like 3MB and refuse to further process anything larger?
FWIW, the now-under-SPO version of the validator processes this (humongous) document, slowly, but surely. I am therefore changing the summary of this bug from: Internal Server Error on Large Document to Limit accepted size of documents, since I quite agree with Bjoern that we may want to play safe. s/blocker/enhancement/, too.