CSE HTML Validator

Hi
it was a batch wizard run with 779 pages. The pages in question was http://www.eden.gov.uk/your-council/how ... -are-made/
Curiously the batch wizard finshed it's job and a report was created. When I try and validate the same page as a single page (i.e not using batch wizard I get a tip saying that one of the lines of that page is 4684 chars long. Could that be the issue? There are no validity errors on that page. ( I do see the warning about it being too old to check from the TNPL though)

I have always thought that the problems we were having were down to memory issues but previous problems have always been shown by the wizard not finishing and an alert dialogue being generated (usually more than 1). I have never seen anything in event viewer.

jscar wrote:Curiously the batch wizard finshed it's job and a report was created.

That's good.

jscar wrote:When I try and validate the same page as a single page (i.e not using batch wizard I get a tip saying that one of the lines of that page is 4684 chars long. Could that be the issue? There are no validity errors on that page. ( I do see the warning about it being too old to check from the TNPL though)

If all is working properly, then the line length should not be a problem, but it is possible that the line length triggered some issue.

jscar wrote:I have always thought that the problems we were having were down to memory issues but previous problems have always been shown by the wizard not finishing and an alert dialogue being generated (usually more than 1). I have never seen anything in event viewer.

It could still be a memory/resource limitation. Less than 1000 pages doesn't seem like too many, but if the computer doesn't have enough resources available or there are a lot of validator messages or the documents are large, then it is more likely to be an issue. One thing I don't think I mentioned is to make sure the OS's virtual memory is working and enabled.

I'm adding some additional checking in v12 that may help determine the cause if this happens again (especially if it's a memory issue where memory cannot be allocated).

Unfortunately this issue is not easily reproducible so it makes it much more difficult to find the cause. I do not think it should be due to your custom TNPL program.

If you'd like to try & test an early BETA of v12, then please let me know.