This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 142 - Limit accepted size of documents
Summary: Limit accepted size of documents
Status: NEW
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.6.1
Hardware: PC Linux
: P2 enhancement
Target Milestone: 1.0
Assignee: Terje Bless
QA Contact: qa-dev tracking
Depends on:
Reported: 2003-02-21 09:47 UTC by Terje Bless
Modified: 2007-05-24 04:57 UTC (History)
0 users

See Also:


Description Terje Bless 2003-02-21 09:47:59 UTC
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
Comment 1 Terje Bless 2003-03-01 14:02:22 UTC
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 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. :-(
Comment 2 Terje Bless 2003-03-01 14:45:05 UTC
Retarget 0.7.0.
Comment 3 Terje Bless 2004-09-01 13:09:42 UTC
Retarget to "1.0"; this wants S:P:O to implement.
Comment 4 Bj 2005-08-18 03:27:06 UTC
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?
Comment 5 Olivier Thereaux 2007-05-24 04:57:27 UTC
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
Limit accepted size of documents,
since I quite agree with Bjoern that we may want to play safe.

s/blocker/enhancement/, too.