memory leak in pickle/cPickle [2.2.3]

[mikemccand]

BPO	770997
Nosy	@birkenfeld

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2005-06-01.11:36:55.000>
created_at = <Date 2003-07-14.15:07:10.000>
labels = ['library']
title = 'memory leak in pickle/cPickle [2.2.3]'
updated_at = <Date 2005-06-01.11:36:55.000>
user = 'https://bugs.python.org/mikemccand'

bugs.python.org fields:

activity = <Date 2005-06-01.11:36:55.000>
actor = 'georg.brandl'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2003-07-14.15:07:10.000>
creator = 'mikemccand'
dependencies = []
files = []
hgrepos = []
issue_num = 770997
keywords = []
message_count = 2.0
messages = ['17053', '17054']
nosy_count = 2.0
nosy_names = ['georg.brandl', 'mikemccand']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue770997'
versions = ['Python 2.2']

[mikemccand]

Smallest case I could come up with:

  import cPickle
  import random
 
  while 1:
    s = str(random.randint(1000000, 9999999))
    a = cPickle.dumps(s)
    cPickle.loads(a)

The leak happens in these cases:

• Python 2.2.2 on FreeBSD 5.0.

• Python 2.2.3 on WinXP.

• Whether you use pickle or cPickle.

The leak does NOT happen:

• With Python 2.3b2 on FreeBSD 5.0 (maybe
  this is a dup of a bug fixed on 2.3b2 --
  can we back-port the fix?)

• If you use binary pickling (change to
  "a = cPickle.dumps(s, 1)" instead).

• If you only call "dumps" or only call "loads";
  somehow, it takes both to leak.

[birkenfeld]

Logged In: YES
user_id=1188172

Doesn't seem to occur in 2.3.5, or 2.4.1.

Closing as Out of Date.