Change by Alex Budovski :
--
nosy: -Alex Budovski
___
Python tracker
<https://bugs.python.org/issue1635741>
___
___
Python-bugs-list mailing list
Unsubscribe:
Alex Budovski added the comment:
Interestingly enough, some of the leaked memory came from the finalize routine
itself! Here's one example:
0:004 !heap -p -a 0x00DB144346F0
address 00db144346f0 found in
_HEAP @ db0cae
HEAP_ENTRY Size Prev Flags
New submission from Alex Budovski:
This means initialize/run script/finalize will crash the second time, since the
inittab can have stale entries.
--
messages: 248495
nosy: Alex Budovski
priority: normal
severity: normal
status: open
title: Py_Finalize doesn't clean up PyImport_Inittab
New submission from Alex Budovski:
This is a known issue, from the comment, but it is causing AVs for my embedded
application when background threads are created, for example, by the _socket
builtin module.
/* Undo the effect of Py_Initialize().
Beware: if multiple interpreter
Changes by Alex Budovski abudov...@gmail.com:
--
type: - crash
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24770
___
___
Python-bugs-list
New submission from Alex Budovski:
The svn commands need to be wrapped with call, otherwise the batch
interpreter hangs. Attached simple fix.
--
files: externalsfix.diff
keywords: patch
messages: 247223
nosy: Alex Budovski
priority: normal
severity: normal
status: open
title