Using time.sleep() in 2 threads causes lockup when hyper-threading is enabled

Marc 'BlackJack' Rintsch bj_666 at gmx.net
Thu May 4 23:14:29 CEST 2006


In <125ir8gpofq3i1c at corp.supernews.com>, Grant Edwards wrote:

> On 2006-05-04, OlafMeding at gmail.com <OlafMeding at gmail.com> wrote:
>> The sleep statement does not return!
> 
> Never, or does it just take a long time?
> 
>> And this should not happen.
> 
> Dude, it's MS Windows.
> 
> It does all _sorts_ of stuff that it shouldn't.
> 
> Having sleep() take orders of magnitude longer than it should
> is not an uncommon complaint for MS Windows users.  There was a
> fairly extensive thread in this group about that problem just a
> few weeks ago.  IIRC, disabling some other program or service
> fixed it for one MS victem.

IIRC it was something like an NTP daemon that caused the clock to "jump"
a little and (Window's) sleep was confused.

Ciao,
	Marc 'BlackJack' Rintsch



More information about the Python-list mailing list