Re: memory problems

From: Silver (bucketofjun_at_dot.com)
Date: 11/27/04

  • Next message: gww: "Intel Pro 100 (82559) on x86" 
    Date: Sat, 27 Nov 2004 17:49:21 GMT

    I would guess that there is a memory leak somewhere in your code eating up
    the heap - coincidentally I think it might be in the software package you
    added.

    There are a couple of tools to walk the heap (LMEMDEBUG being one) that
    might help you. Chances are that it is a coding problem either using the
    library, or in the library itself.

    Geoff 

    --
"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.
>
>
  • Next message: gww: "Intel Pro 100 (82559) on x86"

    Relevant Pages

    • Re: Zeroed pages returned for heap
      ... >>also an application) to assume that the pages returned by the OS for heap ... > memory would seem to be making very dangerous assumptions. ... > pieces of memory to applications without erasing the old contents of the ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Understanding the Garbage Collector
      ... When I run my application it builds a Heap ... When I execute the System.GC.Collect the memory drops back ... System.GC.Collect the memory is never retrieved by the system. ...
      (microsoft.public.dotnet.languages.csharp)
    • Re: Heap allocation
      ... does it get allocated from a per process heap ... System V shared memory and memory mapped files do allow different ... (Read and execute only code loaded from the executable may be ... Death is the worry of the living. ...
      (comp.unix.programmer)
    • Re: Understanding the Garbage Collector
      ... How do you know heap is 200 meg? ... How much memory is surviving to Gen 1? ... When I execute the System.GC.Collect the memory drops back ...
      (microsoft.public.dotnet.languages.csharp)
    • 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)