On 2013-03-09, Roy Smith wrote:
> In article ,
> Grant Edwards wrote:
>
>> What I should have said was that there's no way to return to the OS
>> memory obtained via calls to malloc() et al.
>
> That's true (for certain values of "et al").
>
>> and those are the calls that "good" C programmers (
In article ,
Grant Edwards wrote:
> What I should have said was that there's no way to return to the OS
> memory obtained via calls to malloc() et al.
That's true (for certain values of "et al").
> and those are the calls that "good" C programmers (like the
> maintainers of CPython) use.
Well
On 2013-03-09, Roy Smith wrote:
> In article ,
> Grant Edwards wrote:
>
>> In Unix there is no way to release heap memory (which is what you're
>> talking about) back to the OS except for terminating the process.
>
> That's not quite true. The man page for BRK(2) (at least on the Linux
> box I
In article ,
Grant Edwards wrote:
> In Unix there is no way to release heap memory (which is what you're
> talking about) back to the OS except for terminating the process.
That's not quite true. The man page for BRK(2) (at least on the Linux
box I happen to have handy) says:
"brk() and sbrk
On 2013-03-09, Wong Wah Meng-R32813 wrote:
Your entire post is in your signature block. Don't do that. Many
people have newsreaders or e-mail clinets configured to hide or ignore
signature blocks.
>Yes I have verified my python application is reusing the memory (just
>that it doesn't reduce once
In general, it is hard for any process to return the memory the OS allocate
to it back to the OS, short of exiting the whole process. The only case
that this works reliably is when the process allocates a chunk of memory by
mmap (which is chosen by libc if it malloc or calloc a large chunk of
memo
On 03/09/2013 03:07 AM, Wong Wah Meng-R32813 wrote:
Yes I have verified my python application is reusing the memory (just that it
doesn't reduce once it has grown) and my python process doesn't have any issue to
run even though it is seen taking up more than 2G in footprint. My problem is
c
If the memory usage is continually growing, you have something else
that is a problem -- something is holding onto objects. Even if Python is not
returning memory to the OS, it should be reusing the memory it has if objects
are being freed.
--
[] Yes I have verified my python applicat
The problem is my server hits memory usage threshold, and starts giving me
errors like Oracle unable to spawn off new session stating Out of Memory error
and what not. I won't be bothered much if I have the luxury of available memory
for other processes to use. If only if the UNIX understand my
On Thu, Mar 7, 2013 at 5:33 PM, Wong Wah Meng-R32813
wrote:
> [] The example is written for illustration purpose. Thanks for pointing out a
> better way of achieving the same result. Yes it seems so that the OS thinks
> the piece allocated to Python should not be taken back unless the process
>
Python does not guarantee to return memory to the operating system.
Whether it does or not depends on the OS, but as a general rule, you should
expect that it will not.
for i in range(10L):
> ... str=str+"%s"%(i,)
You should never build large strings in that way. It risks being
On Wed, 06 Mar 2013 10:11:12 +, Wong Wah Meng-R32813 wrote:
> Hello there,
>
> I am using python 2.7.1 built on HP-11.23 a Itanium 64 bit box.
>
> I discovered following behavior whereby the python process doesn't seem
> to release memory utilized even after a variable is set to None, and
>
On 03/06/2013 07:31 AM, Wong Wah Meng-R32813 wrote:
Apologies as after I have left the group for a while I have forgotten how not
to post a question on top of another question. Very sorry and appreciate your
replies.
I tried explicitly calling gc.collect() and didn't manage to see the memory
On 03/06/2013 05:25 AM, Bryan Devaney wrote:
On Wednesday, March 6, 2013 10:11:12 AM UTC, Wong Wah Meng-R32813 wrote:
Hello there,
I am using python 2.7.1 built on HP-11.23 a Itanium 64 bit box.
I discovered following behavior whereby the python process doesn't seem to release memory utili
hmeng=freescale@python.org]
On Behalf Of Terry Reedy
Sent: Wednesday, March 06, 2013 7:00 PM
To: python-list@python.org
Subject: Re: Set x to to None and del x doesn't release memory in python 2.7.1
(HPUX 11.23, ia64)
On 3/6/2013 5:11 AM, Wong Wah Meng-R32813 wrote:
> Hello there,
&
Wednesday, March 06, 2013 6:25 PM
To: python-list@python.org
Cc: python-list@python.org
Subject: Re: Set x to to None and del x doesn't release memory in python 2.7.1
(HPUX 11.23, ia64)
On Wednesday, March 6, 2013 10:11:12 AM UTC, Wong Wah Meng-R32813 wrote:
> Hello there,
>
>
>
On 3/6/2013 5:11 AM, Wong Wah Meng-R32813 wrote:
Hello there,
I am using python 2.7.1 built on HP-11.23 a Itanium 64 bit box.
I discovered following behavior whereby the python process doesn't
seem to release memory utilized even after a variable is set to None,
and "deleted". I use glance tool
On Wednesday, March 6, 2013 10:11:12 AM UTC, Wong Wah Meng-R32813 wrote:
> Hello there,
>
>
>
> I am using python 2.7.1 built on HP-11.23 a Itanium 64 bit box.
>
>
>
> I discovered following behavior whereby the python process doesn't seem to
> release memory utilized even after a variable
Hello there,
I am using python 2.7.1 built on HP-11.23 a Itanium 64 bit box.
I discovered following behavior whereby the python process doesn't seem to
release memory utilized even after a variable is set to None, and "deleted". I
use glance tool to monitor the memory utilized by this process.
19 matches
Mail list logo
