Re: Memory leak in the Driver
- From: "<ctacke/>" <ctacke[@]opennetcf[dot]com>
- Date: Wed, 17 Jan 2007 11:31:39 -0500
Platform Builder wasn't free either, yet you're using it. If your time is
worth anything, then the time saved by using a tool pays for itself quickly.
You've probably already spent more than a day looking for this leak - what
was that day worth?
--
Chris Tacke
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--
"Neo" <rksandilya@xxxxxxxxx> wrote in message
news:1169050226.359701.123650@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Mr. Helge Kruse,
i cannot use ENTREK TOOLBOX, bcoz it is not free !!!
And creating counters is already i did but in my DRIVER i am
deallocating all the memory which i am allocating using localallocand
localfree.
i donot see any free memory in my driver for USB Device.
i did put a print statement with the localalloc and localfree calls
and the corresponding calls matches.
but still when my device is just opened and closes continuosly for 10
times i loose 28KB of memory or so.
can you be able to shed more light on the ToolhelpAPI, i'll try to work
on that !!!
Thanks and Regards,
Neo
Helge Kruse wrote:
The ENTREK Toolbox with CodeSnitch is very useful to find memory leaks in
application.
If this tools does not meet your needs, you can use ToolhelpAPI functions
to
do the work by yourelf. But ... it's work. And you will have to examine
the
results of heap blocks. That's much more work.
Another approach is to create counters fore object creation/deletion. So
you
can find the class with not deleted objects. This can help with the code
review. But this will be application even for driver.
/Helge
.
- Follow-Ups:
- Re: Memory leak in the Driver
- From: Neo
- Re: Memory leak in the Driver
- References:
- Reg : Memory leak in the Driver
- From: Neo
- Re: Memory leak in the Driver
- From: Helge Kruse
- Re: Memory leak in the Driver
- From: Neo
- Reg : Memory leak in the Driver
- Prev by Date: Re: Memory leak in the Driver
- Next by Date: Re: WinCE 5.0 bus driver
- Previous by thread: Re: Memory leak in the Driver
- Next by thread: Re: Memory leak in the Driver
- Index(es):
Relevant Pages
|