Comment 7 for bug 1698090

Revision history for this message
Thayne (thayne-u) wrote :

@Bostjan

I'm really sorry it took so long to get back to you. I just kept putting it off because I was busy, and never got around to testing it.

But we recently ran into this issue again, and tested with building with the --enable-thread-safety configure flag, and that did in fact fix the issue.