JTidy goes into infinite loop on specific input document:
When we call tidy.parse() the stack traces ends in many calls to Node.checkNodeIntegrity()
and the CPU is pegged at 100%
We're using the latest version of JTidy (r938). I've attached a copy of the input document
which triggers the behaviour.
Hopefully it's not too difficult to fix :)
Log in to post a comment.