Re: memory allocation/deallocation problem
From: Eric Sosman (Eric.Sosman_at_sun.com)
Date: 03/17/04
- Next message: Al Bowers: "Re: Accessing a member of a struct via various pointers"
- Previous message: Dan Pop: "Re: working with 8 and 16 bit regions of mem"
- In reply to: Ognen Duzlevski: "Re: memory allocation/deallocation problem"
- Next in thread: CBFalconer: "Re: memory allocation/deallocation problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 17 Mar 2004 10:52:37 -0500
Ognen Duzlevski wrote:
> [reformatted for readability -- if you can't figure out how to
> get your news posting software to keep the lines to a reasonable
> length, consider pressing the ENTER or RETURN key once in a while.]
>
> I have tried to isolate the problem but this function is the
> only place where the memory is allocated and deallocated and it
> seems to be going through the deallocation loop just fine. Another
> interesting thing I just noticed is that if the memory requirements
> are smaller (smaller sequences), even the x86 version of the same
> code seems to show through top that the memory is getting allocated
> and deallocated. It is this huge 1.5 Gb chunk that for some reason
> is not getting freed (and this is not a conclusion from observing
> top but from the fact that the next time around the same function
> fails with insufficient memory).
Have you tried the obvious experiment of reducing your program
to just the allocation and deallocation code? Plus, of course, a
little stub that calls it a few times with appropriate `tlength'
and `qlength' values.
-- Eric.Sosman@sun.com
- Next message: Al Bowers: "Re: Accessing a member of a struct via various pointers"
- Previous message: Dan Pop: "Re: working with 8 and 16 bit regions of mem"
- In reply to: Ognen Duzlevski: "Re: memory allocation/deallocation problem"
- Next in thread: CBFalconer: "Re: memory allocation/deallocation problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|