Hi Ben,

Can you send me the project and source? Let me see what happens on my
machine here....

Rgds,
Jun-Kiat Lam
Metrowerks Technical Support

----- Original Message -----
From: "Ben Gottlieb" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 07, 1999 9:31 AM
Subject: Re: Memory woes with Mac CW....


> >I have been seeing the same thing for years, but never on opening a file,
> >only after I have been running CW for a while and probably gone through
> >20 or 30 compile/link cycles. I have always assumed there's just a memory
> >leak in CW somewhere. For me, simply exiting and restarting CW when I get
> >that message always makes the problem go away.
> >
> >Giving an app more memory won't necessarily help (despite the message),
> >since the internal software may simply allocate a buffer of size X for
> >some function, and it's that buffer which is gradually being "leaked",
> >not necessarily overall memory.
>
> The project opens fine, it's the individual .c files that are the
> problem. It starts with usually the first or second file I open (this
> is just after a restart of the machine) and ONLY happens with this
> project, so I don't *think* it's a memory leak.
>
>
> Ben
>
>
> +--------------------------------------------+
> Ben Gottlieb                           Stand Alone, Inc.
> v: 773-477-2492                 f: 773-477-2579
> [EMAIL PROTECTED]              www.standalone.com
>

Reply via email to