Zachary Ware added the comment:
As far as I can tell, this was an application bug in multiprocessing cleanup 7
years ago. I'm not sure there's really even anything to add to the docs for
this, but if anyone disagrees or produces a patch, please reopen.
--
nosy: +davin, pitrou,
STINNER Victor added the comment:
Serhiy implemented the FileIO class in pure Python: see the issue #21859 (patch
under review).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13081
___
Changes by STINNER Victor victor.stin...@gmail.com:
--
Removed message: http://bugs.python.org/msg222751
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13081
___
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
assignee: - docs@python
components: +Documentation -Windows
nosy: +docs@python
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13081
___
Terry J. Reedy tjre...@udel.edu added the comment:
If I understand the messages, this is more a program bug than a Python bug and
the 'fix' for this tracker would be a doc patch. Adding one would be welcome.
--
nosy: +terry.reedy
___
Python tracker
Amorilia amorilia.game...@gmail.com added the comment:
Thanks for also trying it out, Brian.
I feel there's little more I can do. I guess the multiprocessing module could
be documented a bit better that join() ought to be called before the pool is
deleted? Currently, the docs merely say:
Amorilia amorilia.game...@gmail.com added the comment:
Quick update: apparently, fixing another seemingly unrelated bug, fixed this
crashing issue as well for rlibiez. Here's relevant the commit:
https://github.com/amorilia/pyffi/commit/bd7886eefedfce8fb108c4701cf0467e2a707907
Basically, the
Brian Curtin br...@python.org added the comment:
I tried that script on 2.7 and like it did for you, it just ran until my
machine became unusable.
On 3.x I think I got a RuntimeError after a while, but I forgot exactly what
happened since the machine ended up being hosed later from the 2.7
Amorilia amorilia.game...@gmail.com added the comment:
I'm the author of the application. The tool is written in pure Python, and only
uses libraries from stdlib.
It would be really nice to have a simple standalone script to reproduce the
crash, however I am still trying to reproduce it
Brian Curtin br...@python.org added the comment:
I recently created minidumper to write Visual Studio MiniDump files of
interpreter crashes, but it's currently only available on 3.x. If I port it to
2.x, you could add import minidumper;minidumper.enable() to the top of your
script, then we
Santoso Wijaya santoso.wij...@gmail.com added the comment:
Without the aforementioned minidump library, you can also kick off the Python
interpreter using a debugger (or have a debugger break into an already-running
one) [1]. When the crash happens--presumably the debugger will break at this
Changes by Santoso Wijaya santoso.wij...@gmail.com:
--
type: - crash
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13081
___
___
Python-bugs-list
STINNER Victor victor.stin...@haypocalc.com added the comment:
I suppose that the application uses extensions written in C and one on these
extensions is buggy. Can you write a script to reproduce the bug without the
application? If not, we cannot help you :-(
You may try the faulthandler to
New submission from Roger Libiez arthm...@gmail.com:
While using the application found at:
https://sourceforge.net/tracker/?group_id=199269
The following Windows error dump generates itself while processing a batch of
3D mesh files with it. I do not know the specifics about what process was
14 matches
Mail list logo
