using threads with python and winnt
Aahz Maruch
aahz at netcom.com
Tue Jan 25 06:53:25 EST 2000
In article <000801bf670c$dab7a480$632d153f at tim>,
Tim Peters <tim_one at email.msn.com> wrote:
>
>There's an exceedingly rare timing hole in the released 1.5.2 Python (fixed
>in the CVS version) that had been there for years, showing up in rare
>reports under extremely high rates of thread death and only on top-end
>multiprocessor systems.
We're still using 1.5.1 (no comments, please! we're supposed to finally
upgrade this week), and I was wondering if you could explain what the
symptom of this bug is, because we've seen a couple of recent cases
where a heavily threaded app that creates hundreds of single-shot
threads dies with a thread error.
(We're *also* fixing it to use a thread pool, but I'd still like to know
what our chances are of hitting this with the stock 1.5.2)
--
--- Aahz (@netcom.com)
Androgynous poly kinky vanilla queer het <*> http://www.rahul.net/aahz/
Hugs and backrubs -- I break Rule 6
Have a *HAPPY* day!!!!!!!!!!
More information about the Python-list
mailing list