![](https://secure.gravatar.com/avatar/dff833baff7490517cd9671e8dd553ac.jpg?s=120&d=mm&r=g)
Martijn Faassen wrote:
Hey Stefan,
Yeah, we realize you need a test case. Eric worked quite hard to try to isolate the problem, but no luck yet so far. Hopefully we'll be able to tell you more next week. The situation seems to occur when custom resolvers are involved, and it's conceivable it's not really a threading problem at all.
I *finally* succeeded in building a small (semi) reliable test that shows the behavior. In the end, it has nothing to do with custom resolvers or even xsl:imports, which had me barking up quite a few wrong trees. Enclosed is a small python file, which when run, segfaults pretty reliably for me. I don't think it's doing anything special anymore except the threading. If anyone can help with this, I will be very grateful! eric