On Mon, Aug 6, 2012 at 2:28 PM, Dawid Weiss <[email protected]> wrote: >> + // NOTE: cannot assert this, because on a super-slow >> + // system, it could be after waiting 0.5 seconds that > > Thanks Mike. Interesting because it's not that super-slow windows > machine. A dated 2 core AMD but I wouldn't say it's a snail.
Hmmm well somehow those 2 search threads weren't scheduled (enough) before the 0.5 seconds was up. This was the same case that previously would have lead to deadlock (BG search threads hadn't started before the wait was done). Mike McCandless http://blog.mikemccandless.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
