[ python-Bugs-1006740 ] Possible memory leak in output console

[SourceForge.net]

Bugs item #1006740, was opened at 2004-08-10 12:14
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1006740&group_id=5470

Category: Windows
Group: Platform-specific
Status: Open
Resolution: None
Priority: 5
Submitted By: Kirk Strauser (kstrauser)
Assigned to: Nobody/Anonymous (nobody)
Summary: Possible memory leak in output console

Initial Comment:
I've written a bridge adapter to connect my company's 
Unix servers to our Foxpro database, and it runs as a 
command line program under Python 2.3.4 (with Python 
for Windows Extensions build 202) on a Windows XP 
server.  Basically, it listens for incoming SQL queries from 
the Unix servers (via the Python Web Services 
implementation of SOAP),  executes them with ADODB, 
and returns the results via SOAP. 
 
The system works as desired, except that we've been 
triggering a memory leak with the program has been 
running for long periods of time, to the tune of about .5GB 
of memory per month.  I've recently noticed that the rate 
of leak is proportional to the amount of console output 
that the program generates (the debugging level is 
remotely adjustable via a SOAP method), and that I can 
consistently reclaim the memory by the act of minimizing 
the console window. 
 
That is, at this very moment, the window is minimized 
and the task manager is reporting that the application is 
using 64,908KB of memory. 
 
If I restore the window to its normal size, the memory 
allocation stays about the same. 
 
If I then re-minimize the window, usage drops to 280KB.  
It will then gradually increase again until the server 
begins to bog down, at which point I can repeat the 
process of restoring and then minimizing the console 
window. 
 
In other words, leaving the window "open" does not help, 
nor does leaving it minimized; only the act of minimizing 
an "open" window is sufficient to reduce the 
eternally-growing memory footprint.  This is completely 
reproducible, and I was having the same problem with 
Python 2.3.3 before upgrading it yesterday. 
 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1006740&group_id=5470