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.

classification
Title: suspected cPickle memory leak
Type: Stage:
Components: Library (Lib) Versions: Python 2.2
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: Nosy List: facundobatista, franz2, georg.brandl, loewis
Priority: normal Keywords:

Created on 2005-05-13 15:49 by franz2, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (4)
msg25311 - (view) Author: Alan (franz2) Date: 2005-05-13 15:49
    I believe there is a memory leak in cPickle.  I
have a parallel code which uses array() and indices()
from Numeric to massage data buffers before being sent
and received by Pypar.  Pypar subsequently uses cPickle
to pickle the data.  After many hours of execution, my
code crashes with one of the following error messages
(depending upon the run):


    a = zeros(shape, typecode, savespace)
MemoryError:  can't allocate memory for array


or:


    s = dumps(x, 1)
MemoryError:  out of memory


I have since modified my code to use a different data
format so cPickle is no longer used from PyPar and now
the code runs fine.
msg25312 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2005-05-30 08:34
Logged In: YES 
user_id=21627

Can you provide a test case that demonstrates how the memory
is exhausted? Without a test case, it is unlikely that we
will be able to find the suspected leak.
msg25313 - (view) Author: Facundo Batista (facundobatista) * (Python committer) Date: 2005-05-30 20:34
Logged In: YES 
user_id=752496

Please, could you verify if this problem persists in Python 2.3.4
or 2.4?

If yes, in which version? Can you provide a test case?

If the problem is solved, from which version?

Note that if you fail to answer in one month, I'll close this bug
as "Won't fix".

Thank you! 

.    Facundo
msg25314 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2005-09-14 20:18
Logged In: YES 
user_id=1188172

Closing due to lack of response. cPickle is such a complex
module, without a test case the leak cannot be found.
History
Date User Action Args
2022-04-11 14:56:11adminsetgithub: 41980
2005-05-13 15:49:18franz2create