Re: T_MEMORYRELEASED
Re: T_MEMORYRELEASED
- Subject: Re: T_MEMORYRELEASED
- From: email@hidden
- Date: Tue, 26 Feb 2002 12:46:50 -0500
On Tuesday, February 26, 2002, at 11:30 , Jim Myers wrote:
The T_MEMORYRELEASED message just lets you know that memory you
allocated
and released via OT's memory allocation has been returned to the heap
and
the pointer previously given to that block of memory is no longer valid.
My code sets the pointer/variable I use to NULL so that I don't access
the now invalid pointer without allocating RAM again.
Umm, that's not right, is it? My understanding was that T_MEMORYRELEASED
is sent when OT wants to tell you that a chunk of memory (not
necessarily a heap block or memory pool block, just a range of bytes) is
no longer being looked at by OT. When you have AckSends turned on, OT
doesn't copy the data when you sent it, and instead uses your buffer
until it's done with it. Then it sends that message. I would think that
if you're interpreting that as OT saying that it's freed a heap block,
then you're leaking a lot of memory. Of course, please correct me if I'm
wrong.
Philip D. Wasson
email@hidden
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.