Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!trwind!venice!press
From: press@venice.SEDD.TRW.COM (Barry Press)
Newsgroups: comp.windows.ms
Subject: Re: <None>
Message-ID: <1010@venice.SEDD.TRW.COM>
Date: 25 Feb 91 17:28:24 GMT
References: <2606.27c462bf@incstar.uucp>
Reply-To: press@venice.sedd.trw.com (Barry Press)
Organization: TRW Systems Engineering & Development Division, Redondo Beach, CA
Lines: 25

In article <2606.27c462bf@incstar.uucp> noyce@incstar.uucp writes:
>Just a general question - It appears that if you work in Win 3.0 for
>a long time, doing multiple document open/close, either in Excel 2.1d
>or Word 4 Windows, that eventually, memory gets so fragmented, that
>Win 3.0 appears to 'run out' of memory.  At this point,  I have found
>that the only way to re-coupe this memory, is to exit Win 3.0 to the
>C:> prompt, then re-enter Windows.  While this isn't a major problem,

Iv'e seen this happen, but there seem to be two mechanisms at work, only one
of which I can clearly point a finger at:

1.	Some applications fail to properly release memory and/or other
resources they use.  Windows can't necessarily solve this problem, and as
more and more of that garbage shows up, it may eventually run out.  This
doesn't have to be global memory -- it can just as easily (or more so) be
memory in the heap for the USER DLL, which holds many graphics-related
items and is limited to 64K in Win3.0.  Not much for this, except to restart
windows as you note.

2.	I've also seen situations where I received the "not enough memory" 
message, immediately tried the same launch, and succeeded.  No clue as to
what happened in these cases.

-- 
Barry Press                                 Internet: press@venice.sedd.trw.com