This a great piece of technology, but why, when I'm running a very large scan -- say 7500 pages -- does eValid get "stuck" part way through?

You have to be careful to determine whether eValid "got stuck" or whether the page at which eValid appears to be stuck is correct.

eValid, being a quality assurance tool, is by design quite intolerant of things like poorly formed JavaScript (JScript) and other kinds of common problems.

In our experience the only thing that stops an eValid site analysis scan is when you encounter a "bad page", or when you have so many pages that you run out of CPU time and/or memory, but that limit is evidenced by a different kind of symptom: the computer just slows down and finally grinds to a halt with "out of memory" messages.

eValid Support