Am Donnerstag 11 Mai 2006 18:07 schrieb Michele Petrazzo:
> Heiko Wundram wrote:
> > As was said before: as long as you keep a reference to an object, the
> > object's storage _will not be_ reused by Python for any other objects
> > (which is sensible, or would you like your object to be overwritte
Fredrik Lundh wrote:
> bruno at modulix" wrote:
>
>
>>*please* re-read carefully what I and Diez wrote earlier in this thread
>>before jumping to possibly erroneous conclusion. I didn't say that the
>>problem *actually* was with Python - just that it *may* have to do with
>>a memory management is
Heiko Wundram wrote:
> PIL isn't known to have any memory leaks, by the way (AFAICT), just to confirm
> what I've written before, but the effbot should be of more help here...
PIL is heavily used in 24/7 production systems, often by people who knows a lot
about how to run mission critical systems
bruno at modulix" wrote:
> *please* re-read carefully what I and Diez wrote earlier in this thread
> before jumping to possibly erroneous conclusion. I didn't say that the
> problem *actually* was with Python - just that it *may* have to do with
> a memory management issue fixed in 2.5.
the only
mardif a écrit :
> OK! i will test my app with python 2.5a2
Please let us know the result.
--
http://mail.python.org/mailman/listinfo/python-list
OK! i will test my app with python 2.5a2
thx
--
http://mail.python.org/mailman/listinfo/python-list
[Serge Orlov]
> BTW python 2.5 now returns free memory to OS, but if a program keeps
> allocating more memory with each new iteration in python 2.4, it will
> not help.
No version of CPython ever returns memory to "the OS". All memory is
obtained via the platform C's alloc() or realloc(), and any
mardif wrote:
> In python 2.5 this was resolved, ok, but i can't use any python version
> then 2.3.5.
>
> This project was initializated with this version, and now it can be
> dangerous change version, even because I use McMillan installer for
> compile e build an executable.
Err... I'm sorry I do
Heiko Wundram wrote:
> As was said before: as long as you keep a reference to an object, the object's
> storage _will not be_ reused by Python for any other objects (which is
> sensible, or would you like your object to be overwritten by other objects
> before you're done with them?). Besides, eve
mardif wrote:
> In python 2.5 this was resolved, ok, but i can't use any python version
> then 2.3.5.
> This project was initializated with this version, and now it can be
> dangerous change version, even because I use McMillan installer for
> compile e build an executable.
>
> So, my initial win
In python 2.5 this was resolved, ok, but i can't use any python version
then 2.3.5.
This project was initializated with this version, and now it can be
dangerous change version, even because I use McMillan installer for
compile e build an executable.
So, my initial window is a "menu window", when
[EMAIL PROTECTED] wrote:
> Ok, this is true.
>
> Well, you consider that my app has a first windows, where I choose, for
> example, the application 1.
> The application 1 will be started, and it will allocate 200Mb total.
> Now I want to abort this operation, and i will return to main initial
> w
Heiko Wundram wrote:
> Am Donnerstag 11 Mai 2006 15:15 schrieb [EMAIL PROTECTED]:
> > I MUST find a system which deallocate memory...
> > Otherwise, my application crashes not hardly it's arrived to
> > break-point system
>
> As was said before: as long as you keep a reference to an object, the ob
Am Donnerstag 11 Mai 2006 15:15 schrieb [EMAIL PROTECTED]:
> I MUST find a system which deallocate memory...
> Otherwise, my application crashes not hardly it's arrived to
> break-point system
As was said before: as long as you keep a reference to an object, the object's
storage _will not be_ re
Ok, this is true.
Well, you consider that my app has a first windows, where I choose, for
example, the application 1.
The application 1 will be started, and it will allocate 200Mb total.
Now I want to abort this operation, and i will return to main initial
window. The memory usage remain to 200Mb
<[EMAIL PROTECTED]> wrote:
>If I write:
>
>a = range(500*1024)
>
>I see that python process allocate approximately 80Mb of memory.
>What can i do for DEALLOCATE this memory, or good part of this?
> [ ... ]
>I've tried with Destroy, del command, but the memory don't show down.
It won't (much). Whe
Well, it's right about range diff xrange, ok, but this was a simple
example...
I repeat that my program don't work with range or xrange...
I MUST find a system which deallocate memory...
Otherwise, my application crashes not hardly it's arrived to
break-point system
--
http://mail.python.org/ma
[EMAIL PROTECTED] wrote:
> Hi,
> I've a big memory problem with my application.
>
> First, an example:
>
> If I write:
>
> a = range(500*1024)
>
> I see that python process allocate approximately 80Mb of memory.
> What can i do for DEALLOCATE this memory, or good part of this?
>
> My really p
O
I see
--
http://mail.python.org/mailman/listinfo/python-list
Hi,
'del a' should remove 'a', as a reference to the tuple created by the
'range' function.
If that is also the last reference, it can now be garbage-collected.
Of course, the question is if you really need to allocate such a big
amount of memory. If you just need to iterate over some numbers, it
20 matches
Mail list logo
