Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!emory!att!chinet!patrickd
From: patrickd@chinet.chi.il.us (Patrick Deupree)
Newsgroups: comp.windows.ms
Subject: Re: Windows slow down after use
Keywords: slow
Message-ID: <1990Jan10.004609.18604@chinet.chi.il.us>
Date: 10 Jan 90 00:46:09 GMT
References: <15414@well.UUCP>
Reply-To: patrickd@chinet.chi.il.us (Patrick Deupree)
Distribution: comp
Organization: Chinet - Chicago Public Access UNIX
Lines: 17

In article <15414@well.UUCP> berger@well.UUCP (Robert J. Berger) writes:
}Has anyone had a problem where their windows application begins to slow down
}after extended use? The acutal painting of the windows and their data slows
}down to where you can actually see it updating the screen.

You're hosing Windows memory someplace.  Basically, when Windows gets slow it
usually means that it's starting to thrash.  This in turn means that your
conventional memory is going down.  Check to see if you're getting context
without releasing context, if you're not releasing resources, if you're doing
GlobalAlloc's without getting rid of the space you've allocated, etc.  There
are a million reasons this could happen, but you've got to track down where
you're not freeing memory.
-- 
"I place my faith in fools.  Self confidence, my friends call it."
					-Edgar Allen Poe

Patrick Deupree -> patrickd@chinet.chi.il.us