Message11510

I've now seen this exception raised in the "parse" and "json" cases on my Linux system. They are rare for me. No program I have is guaranteed to raise one.
I tentatively observe:
1. They are more likely to occur early in execution (if they occur at all).
2. Often I get no actual concurrency (only 1 or 2 more threads than daemons in jvisualvm).
3. Attempting to catch the exception (almost) stops it happening :(
I prefer the parse example as it ought to be possible to preserve the crime scene.
I have a version of the program that (really) runs 100 threads, parsing 2000 foo/bar elements, and drops into pdb if it raises. I'm repeatedly launching it in a Bash while loop. No luck yet.