Re: Memory leak in the Driver

Have you applied all of the Platform Builder QFEs?

Paul T.

"Neo" <rksandilya@xxxxxxxxx> wrote in message
news:1169060894.231009.199230@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,

Also i want to know whether there are any known leaks in the platform
builder 5.0(WinCE5.0) Edition.
i am developing USB-Serial Driver which uses both USB related functions
and also the Serial related Code.
are there any known memory leaks in other dll's which will used in
usb-serial driver development.

Thanks and Regards,
Neo

Neo wrote:
Hi Mr.Chris Tacke

As of now i cannot get that tool in for me.
Anyway it is since a week i was trying to find this leak !!!!
i can understand what u said and it's right too !!!

but i need to go thru the normal way of debugging and i am limited by
my resources !!!
hoping for more support from you guys !!!

Thanks and Regards,
Neo

<ctacke/> wrote:
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




.

Relevant Pages
Loading