Rock Achu added the comment:
Erm.. No. I was unaware I had to do so.
Next time I'll be more careful.
Anyways, the docs say that python should throw a RuntimeError, but it didn't?
And would it be doable to add a warning at the top of the multiprocessing
tutorial/page th
Rock Achu added the comment:
Alright. Just running:
import multiprocessing
thread = multiprocessing.Process()
thread.start()
raw_input()
-
Causes the crash. This time there is no output, so it is essentailly invisible.
Caught me by surprise
Rock Achu added the comment:
Alright. The issue stays here. Passing nothing to multiprocessing.Process still
reproduces the issue.
someone else know how to deal with this?
--
___
Python tracker
<http://bugs.python.org/issue13
Rock Achu added the comment:
Changing the function name and removing the argument (self) passed to func
doesn't change a thing.
--
___
Python tracker
<http://bugs.python.org/is
Rock Achu added the comment:
More clues:
the function _M_Process.func isn't being called.
--
___
Python tracker
<http://bugs.python.org/is
Rock Achu added the comment:
By inserting print statements and feverishly killing the process, I narrowed it
down to the statement:
self.thread.start()
that causes the issue.
which runs _M_Process.func() in a multiprocessing.Process
--
___
Python
Rock Achu added the comment:
Ok, using other code, I narrowed it down to this code and before:
for i in xrange(10):
spawner.newproc(run=True)
repeating infinitely
which only should set a variable (self.busy) to false
--
___
Python tracker
Rock Achu added the comment:
Or did I only have 20 threads?
if the program was running in a loop, then it would have spawned 20 threads
each, leading to the huge amount of processes, and probably the other issues.
So why does it run so many times
Rock Achu added the comment:
On a hunch opened task manager. There were over 9000 python processes open.
Shocking.
That was probably the cause of the system freeze.
However I only had 20 threads open. Why so many processes?
--
___
Python tracker
Rock Achu added the comment:
I hit Ctrl-C right after opening the bat file and got this mess:
--
Added file: http://bugs.python.org/file24109/error.txt
___
Python tracker
<http://bugs.python.org/issue13
New submission from Rock Achu :
running this script repeatedly causes corruption in the console window.
Just before posting this report, it led to a complete windows system freeze.
running python 2.7 x86 on windows x64.
The programs seems to run a couple times (when it is supposed to run
11 matches
Mail list logo
