NewLC - Tracking down memory leaks - Comments

Tracking down memory leaks

kavita — Fri, 25 May 2007 12:31:10 +0200

Its very nice way of finding out memory leak... but i am facing some problem.

I found that leak is occuring at 0x372B0244 this address and i found that the module with memory block of same address

I did "view memory" and typed 0x372B0244 address....by putting breakpoint at all possible places...and it did not display any msg instead it showed ...i... @ ...
Nothing came in red color...

How can i find out leak...
pls tell me if u have some more tips or logics...

Thanks

> Tracking down memory leaks

Anonymous — Fri, 27 Jan 2006 21:11:28 +0100

Symbian Hooklogger should do the trick?

http://www.symbian.com/developer/downloads/tools.html#HookLogger

> Tracking down memory leaks

Anonymous — Sat, 21 Jan 2006 07:51:01 +0100

Hi Eric,

Indeed a good article, only one thing in mind.

When i access the internet (wap etc..) through "Services" on the emulator it gives alloc error on exit.

Similarly any app that accesses the internet gives alloc errors on exit on the emulator (but not on device).

Why so?

And can something be done abt such apps regarding coding so that that alloc does not come up?

Thanks.

> Tracking down memory leaks

alh — Thu, 12 Jan 2006 17:24:32 +0100

Another good tip, if the memory adress is this predictable, is to at the destructor breakpoint, typecast the memory address to a CBase* in your debugger watch window.

Add a watch: (CBase*)(0x1428f900)

And, if the orphaned cell is a subclass of type CBase, you will be able to unfold it in the watch window, and see its real type.

Tracking down memory leaks

eric — Thu, 12 Jan 2006 11:50:50 +0100

Your application terminates with an ugly "Program Closed: ALLOC xxxxxxxx 0" window ? It has leaked some memory... this article will teach you how to track down the faulty allocation.