Changes by Xavion <xavio...@gmail.com>:
Added file: http://bugs.python.org/file44763/Test-3a-gc.log
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by Xavion <xavio...@gmail.com>:
Added file: http://bugs.python.org/file44762/Test-3a-no-gc.log
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Xavion added the comment:
Firstly, you've misquoted me. The quote you attributed to me in your latest
post was actually made by 'ztane'.
Secondly, your extra thread/event code makes no difference here. I will attach
the memory usage logs in subsequent posts.
For consistency, I have removed
Xavion added the comment:
haypo: So, what is the result when you run "Test-2.py" and monitor the memory
usage with "Test.sh"?
ztane: The code you've provided is the same as "Test-1.py". You need to run
"
Xavion added the comment:
What about when you test it using the files I provided? I didn't want you guys
to have to write your own code.
Note that I was monitoring the memory externally (via good old 'ps'). This
could make a difference to the outcome
Xavion added the comment:
Wow, that is surprising (given how simple it is)! Did you try both tests?
Remember that only the second one produces the bug here.
Let's leave this sit for a while. If no-one else can reproduce it on their
OSs/distributions, I'll seek advice from the Arch
Changes by Xavion <xavio...@gmail.com>:
Added file: http://bugs.python.org/file44730/Test-2-gc.log
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by Xavion <xavio...@gmail.com>:
Added file: http://bugs.python.org/file44729/Test-2-no-gc.log
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by Xavion <xavio...@gmail.com>:
Added file: http://bugs.python.org/file44727/Test-1-no-gc.log
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by Xavion <xavio...@gmail.com>:
Added file: http://bugs.python.org/file44726/Test-2.py
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by Xavion <xavio...@gmail.com>:
Added file: http://bugs.python.org/file44728/Test-1-gc.log
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by Xavion <xavio...@gmail.com>:
Added file: http://bugs.python.org/file44724/Test.sh
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by Xavion <xavio...@gmail.com>:
Added file: http://bugs.python.org/file44725/Test-1.py
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Xavion added the comment:
I put them into an archive so that the folder hierarchy would be preserved.
Doing it that way makes it faster for you guys to run the tests at your end.
Nonetheless, I will post the seven (7) files individually as well. It doesn't
look like I can upload more than
Changes by Xavion <xavio...@gmail.com>:
Removed file: http://bugs.python.org/file44708/Memory-Leak-Test.zip
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Xavion added the comment:
Okay, I've modified the title to match what I've written below.
I've just run some further tests on this problem. The attached archive
contains code samples and the output generated (both with and without garbage
collection).
As you can see, the memory stays
Changes by Xavion <xavio...@gmail.com>:
Removed file: http://bugs.python.org/file44672/Output.log
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Xavion added the comment:
It's easier to reproduce the issue if you use a timer (rather than a loop).
The newly attached logfile was generated with the following code fragment.
def fTest() :
check_output("true")
threading.Timer(1, fTest, ()).start()
--
Changes by Xavion <xavio...@gmail.com>:
Removed file: http://bugs.python.org/file44671/Output.log
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Xavion added the comment:
I wouldn't have reported this if it was only happening *once*. I already have
it in a loop; a new shell command is fired every second.
The memory footprint increases by roughly 4 KiB *each* time. I monitor it via
the following Bash script:
while true; do
New submission from Xavion:
Each time I run a shell command via the 'subprocess' module, I notice that the
memory footprint of my program increases by roughly 4 KiB.
I've tested the problem with two different slices of code; the result is the
same in either case (long after the function
21 matches
Mail list logo
