Am Dienstag, 4. November 2008 20:06:11 schrieb vicente.botet:
The code using fibers sometimes raises an assertion in ~mutex() (used in work-stealing queue). For this reason and following the discussions I think I'll remove the support for fibers from threadpool.
Why not. I was not really attached to this solution.
The usage of fibers in threadpool v12 did not provide any benefit realted to invoking tasks recursivly (it is slower because of its syste mcalls). I've enabled fiber migration to other worker-threads (stealing) inv v13. But I get runtime errors like discussed in the discussions in the mailing list (for instance pobs with locked mutexes in fibers). Maybe I've also some implementation bugs - the code using fibers is not stable. I'm open for discussion. regards, Oliver