From: Pascal Dennerly (dnnrly_at_[hidden])
Date: 2008-04-21 09:02:26
If you're churning at 100% utilisation, does that mean that the worker
thread loop isn't waiting between iterations? Could this thread be blocking
which ever thread is feeding into it just by hogging the processor?
On 4/21/08, Peter Dimov <pdimov_at_[hidden]> wrote:
> >> How often, on what platform?
> > Every time, on a dual core Pentium D running XP64. The program is
> > as 32 bit with MSVC 7.1. It looks like a livelock rather than a
> > since the program keeps spinning its wheels at 100% but never completes.
> > The writer thread is probably either blocked or starved. This happens on
> > another (quad core) machine too for which I don't know the specs at the
> > moment.
> The other box is XP32 w/ Q6600.
> Another interesting tidbit is that if I move the focus from the cmd window
> in which the test is running, it completes. Go figure.
> The writer thread is likely being starved, no idea why or how.
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk