Memory leak with datetime used with time.strptime

[sebegue]

BPO	4620
Nosy	@smontanaro

^{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 2008-12-11.14:46:07.394>
created_at = <Date 2008-12-10.14:40:40.436>
labels = ['performance']
title = 'Memory leak with datetime used with time.strptime'
updated_at = <Date 2008-12-11.14:46:07.392>
user = 'https://bugs.python.org/sebegue'

bugs.python.org fields:

activity = <Date 2008-12-11.14:46:07.392>
actor = 'skip.montanaro'
assignee = 'none'
closed = True
closed_date = <Date 2008-12-11.14:46:07.394>
closer = 'skip.montanaro'
components = ['None']
creation = <Date 2008-12-10.14:40:40.436>
creator = 'sebegue'
dependencies = []
files = []
hgrepos = []
issue_num = 4620
keywords = []
message_count = 5.0
messages = ['77543', '77550', '77551', '77577', '77614']
nosy_count = 4.0
nosy_names = ['skip.montanaro', 'ggenellina', 'quentin.gallet-gilles', 'sebegue']
pr_nums = []
priority = 'normal'
resolution = 'works for me'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'resource usage'
url = 'https://bugs.python.org/issue4620'
versions = ['Python 2.5']

[sebegue]

When I use the following line in my process (my process run these line
each 10 seconds), memory size increases progressively :
myDate = datetime.datetime(*(time.strptime(dateString,
"%Y-%m-%dT%H:%M:%S")[0:6]))

the '*' operator unpacks the tuple, producing the argument list for
datetime.datetime but it seems that the structure return by
time.strptime is not correctly flushed in memory.

[smontanaro]

Can you reproduce this with a script that does nothing more
than

while True:
  myDate = datetime.datetime(*(time.strptime("2008-12-10T14:00:03",
"%Y-%m-%dT%H:%M:%S")[:6]))

I tried with both Python 2.4.5 on Solaris and Python built from
CVS (aka 2.7a0) on my Mac and see no memory growth of the
processes. If there's a memory leak my guess is that it is
somewhere else.

[quentingallet-gilles]

Tried it with Python 2.5.2 on WinXP, I see no memory growth either.

[ggenellina]

After running for more than 2 hours, I could not see any memory growth
with 2.5.2 on WinXP.

[smontanaro]

A number of people on a number of platforms and versions can't reproduce
this.