Message 23835 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Recipients
Author	bob.ippolito
Date	2005年01月01日.06:18:59
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
Logged In: YES user_id=139309 I can't reproduce this on either version of Python a 10.3.7 machine w/ 1gb ram. Python's total memory usage seems stable to me even if the read is in a while loop. I can't see anything in sock_recv or _fileobject.read that will in any way leak memory. With a really large buffer size (always >17mb, but it does vary with each run) it will get a memory error but the Python process doesn't grow beyond 50mb at the samples I looked at. That's pretty much the amount of RAM I'd expect it to use. It is kind of surprising it doesn't want to allocate a buffer of that size, because I have the RAM for it.. but I don't think this is a bug.

Content

Logged In: YES 
user_id=139309
I can't reproduce this on either version of Python a 10.3.7 machine w/ 
1gb ram. Python's total memory usage seems stable to me even if the 
read is in a while loop.
I can't see anything in sock_recv or _fileobject.read that will in any way 
leak memory.
With a really large buffer size (always >17mb, but it does vary with each 
run) it will get a memory error but the Python process doesn't grow 
beyond 50mb at the samples I looked at. That's pretty much the amount 
of RAM I'd expect it to use. 
It is kind of surprising it doesn't want to allocate a buffer of that size, 
because I have the RAM for it.. but I don't think this is a bug.

History
Date	User	Action	Args
2007年08月23日 14:28:47	admin	link	issue1092502 messages
2007年08月23日 14:28:47	admin	create

homepage