Created attachment 1142511 [details]
The test case for this upstream bug:
exercises a different code path as well, and crashes occasionally even if swbz#12847 is fixed.
This was corrected in this upstream commit, which is currently missing in Red Hat Enterprise Linux 6:
Author: Ulrich Drepper <firstname.lastname@example.org>
Date: Fri Sep 9 16:15:25 2011 -0400
Don't lock string streams in stream cleanup code
The attached test case triggers this bug about 80% of the time on my test VM. It has to be run in a shell script, like this:
for x in `seq 1 100` ; do
This bug is not relevant to my use case as described in bug 1275384.