Hi Lukas, On Fri, May 09, 2014 at 12:40:11PM +0200, Lukas Tribus wrote: > Can the 100% cpu load initially reported along with the segfaults be > explained by the unsupported process shared mutex on FreeBSD, btw?
Absolutely. Some lists are updated within the lock. I let you imagine what a double-linked list looks like when two writers access it at the same time :-) Sometimes we used to get an outdated pointer resulting in a segfault, sometimes a loop resulting in 100% user-space cpu. Willy
