The destructor for AtomicStringList is recursive, and can run out of stack space when the number of classes is too high. Load the test url, then close the window or reload to trigger the crash. The testcase is currently 14MB; I haven't yet determined what the cutoff point where it stops crashing is. A reasonable solution (which I hope to find time to try) would be to make AtomicStringList be Vector based instead of a linked list.
This was probably fixed in r28722 which switched the data structure to use a Vector. David, can you verify this.
This is fixed as of r28722 :)