Heritrix: Internet Archive Web Crawler

Seen in FR crawl:

<<<
java.lang.StackOverflowError
#8
http://www.gltrade.fr/gltcom/servlet/com.gltrade.gltcom.menu.GlTradeQuoteSe
rvlet?menu=investors
(0 attempts)
REL
Current processor: ExtractorHTML
ACTIVE for 9s498ms
Where: ABOUT_TO_BEGIN_PROCESSOR for 1460ms

java.lang.StackOverflowError
at
java.lang.Character.codePointAt(Character.java:2336)
at
java.util.regex.Pattern$BitClass.match(Pattern.java:2873)
at
java.util.regex.Pattern$Sub.match(Pattern.java:5246)
at
java.util.regex.Pattern$Sub.match(Pattern.java:5246)
at
java.util.regex.Pattern$Sub.match(Pattern.java:5246)
at
java.util.regex.Pattern$Sub.match(Pattern.java:5246)
at
java.util.regex.Pattern$Curly.match(Pattern.java:4189)
at
java.util.regex.Pattern$Single.match(Pattern.java:3314)
at
java.util.regex.Pattern$GroupHead.match(Pattern.java:4569)
at
java.util.regex.Pattern$Loop.match(Pattern.java:4696)
at
java.util.regex.Pattern$GroupTail.match(Pattern.java:4628)
at
java.util.regex.Pattern$Curly.match0(Pattern.java:4234)
at
java.util.regex.Pattern$Curly.match(Pattern.java:4196)
at
java.util.regex.Pattern$Single.match(Pattern.java:3314)
at
java.util.regex.Pattern$GroupHead.match(Pattern.java:4569)
at
java.util.regex.Pattern$Loop.match(Pattern.java:4696)
at
java.util.regex.Pattern$GroupTail.match(Pattern.java:4628)
at
java.util.regex.Pattern$Curly.match0(Pattern.java:4234)
at
java.util.regex.Pattern$Curly.match(Pattern.java:4196)
at
java.util.regex.Pattern$Single.match(Pattern.java:3314)
at
java.util.regex.Pattern$GroupHead.match(Pattern.java:4569)
at
java.util.regex.Pattern$Loop.match(Pattern.java:4696)
at
java.util.regex.Pattern$GroupTail.match(Pattern.java:4628)
at
java.util.regex.Pattern$Curly.match0(Pattern.java:4234)
at
java.util.regex.Pattern$Curly.match(Pattern.java:4196)
at
java.util.regex.Pattern$Single.match(Pattern.java:3314)
[plus lots more, but not all the way to see which
regexp was being applied]

Could NOT reproduce with current version of page on
live web, even though it does have some atypically
long/intricate <param> tags.

StackOverflowError caused crawl to pause, as it was
treated same as OOME. But, this error should usually be
recoverable, only harming the current thread/URI. So,
crawl should shake it off like other RuntimeExceptions.