19 Dec
2002
19 Dec
'02
7:30 p.m.
Jean-Francois.Doyon@CCRS.NRCan.gc.ca writes:
I most definitely use Python 2.1.3 ...
I however AM using 2.5.0 ... A bit old I know, I'm about to start working on upgrading when 2.6.1 comes out ...
Are there specific bugs in 2.5.0 that could be causing this behavior? I vaguely recall looking at the Change Log and Collector, but not finding much about any kind of memory leak ... I do not know about leaks.
But, I know about a bug in "cAccessControl" that can lead to memory corruption (and subsequent SIGSEGV termination). Dieter