Re: memory problems

From: Paul G. Tobey [eMVP] (ptobey)
Date: 11/29/04 

Date: Mon, 29 Nov 2004 10:03:51 -0700

Entrek Toolbox will help debug memory leak problems of this sort. It's an
excellent tool!

Paul T.

"Boyd D. Mills" <BMills@VCIControls.ca> wrote in message
news:u3S2$e90EHA.2192@TK2MSFTNGP14.phx.gbl...
> Hi,
> I am using a PB4.1 CEPC image build on a 64Meg Pentium PC104 board.
> It seems coincidental that the problem has started since I stated using a
> software library package that makes extensive use of "LocalAlloc( LPTR,
> nbytes )" and "LocalFree( p )." I find this an odd coincidence since
> several drivers use these memory manipulation calls as well so this may be
> a moot observation.
>
> The symptom is that after some indeterminant length of time
> (minutes/hours/days) I will subsequently get error messages when trying to
> start new applications:
>
> "Cannot execute 'cmd'. A critical component is either missing or failing
> to start due to low memory."
>
> Applications that are running during this state continue to function with
> no perceived problems.
>
> This is less than helpful since sometimes I can get the system information
> dialog box to display while the machine is in this state. It indicates
> there is about 25Meg of application memory available and about 20Meg of
> data memory available. So I don't think the total available memory is an
> issue.
>
> I am not familiar with the internals of the CE4.1 memory management. Is
> it possible the memory has become too fragmented to allow a new
> application to execute? ( A wild guess. )
>
> Any idea as to the cuase of this issue or a possible solution.
>
>

Relevant Pages

  • Re: News on HST2
    ... Yesterday's high level languages simply won't produce the sort of applications we are used to seeing now. ... Given the vast change in bangs per buck over the years, trying to squeeze every last bit out of memory no longer makes economic sense - it's cheaper to just stick more memory in than pay for the extra coding cost. ...
    (uk.railway)
  • Re: xmalloc string functions
    ... require memory allocations depending on the way the system works. ... If the toolkit being used is not one of those, then it is irrelevant that some provide a means to do so, particularly if the "some" are not available for the platform being targeted. ... Not enough context for most real-world applications to recover at this point. ... At this point g_malloccalling abortbecomes a moot point, particularly if your auto-save code is robust against memory allocation errors. ...
    (comp.lang.c)
  • Re: ProDOS Plus
    ... operating system was not considered worth the problems when it was just as easy to make the applications support 128k or more ram. ... your suggested P-code system could do something similar by running in the aux 64k memory range $D000...FFFF or perhaps the aux ram used by the P8 /ram driver code space. ... the OS could fit in *only* the space that ProDOS now occupies. ... if practicality were a concern we probably wouldn't be using old hardware. ...
    (comp.sys.apple2)
  • Re: xmalloc string functions
    ... If these were the only choices (crashing applications or a frozen ... trying to malloc some rediculously large amount of memory - e.g. in the ... because their malloc wrapper decided to exit. ... Exiting on malloc failure makes sense for a utility like sort. ...
    (comp.lang.c)
  • Re: xmalloc string functions
    ... require memory allocations depending on the way the system works. ... Not enough context for most real-world applications to ... It is /more/ reliable to routinely auto-save the user's work (as you ... particularly if your auto-save code is robust against memory allocation ...
    (comp.lang.c)