LPP> I spawned a thread that does some heavy slot access. So maybe LPP> the serializer isn't entirely multi-thread or multi-process safe LPP> yet?
maybe. there were some issues with it (trivial ones), who knows, maybe we've overlooked something. if you have a multi-core system and value stability over performance, i strongly recommend binding you lisp process to a single core (via taskset in Linux, for example). this way multithreading-related issues will have much less chances to happen. there could be issues with SBCL itself, SBCL developers do not claim that they have 100% thread-safe code in all places, and i've seen some version of SBCL crashing under multithreaded load. _______________________________________________ elephant-devel site list elephant-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/elephant-devel
