>Hi all,
>
[quoted text clipped - 11 lines]
>copy a large file and delete , then u will see must more memory lost.
>Would be really grateful if anybody could help.
I'm definitely not the best person to answer, but maybe better than no
one. I haven't kept close track, but last I heard, garbage collection
is slow for Windows CE (and thus Windows Mobile). So the leak you
detected may be temporary. My apps copy files quite a bit with no
noticeable leak.
-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).
Robert E. Zaret, eMVP
PenFact, Inc.
20 Park Plaza, Suite 478
Boston, MA 02116
www.penfact.com
Magneto - 30 Jul 2008 18:50 GMT
> >Hi all,
>
[quoted text clipped - 19 lines]
>
> Thanks Robert for your reply, I did check if the memory leak remains for sometime and frees up, but it does not,
it frees up only after reset, I see the memory leak is about 200kb,
is this fine and normal? i am seeing the memory usage from
the control panel, system memory. I also run the App verifier , in
which i run the filesys.exe, i got the following log, but i assume the
filesys.exe is always running and does not stop , so maybe the log
below is not right, is device.exe also invloved in file creation and
deletion?,
As i know in our platform, what ever we store on the desktop , it gets
stored onto our flash, could the filsytem (FatFS) have any problem,
I would really appreciate your help
# LOGENTRY shim_heap.dll 13 'Non-destroyed heap
The application created a heap, and did not destroy it.
# DESCRIPTION END
# LOGENTRY shim_heap.dll 14 'Can't destroy process heap
# DESCRIPTION BEGIN
The application attempted to destroy the process heap.
# DESCRIPTION END
# LOGENTRY shim_heap.dll 15 'Injected a heap fault
# DESCRIPTION BEGIN
The shim is injecting a heap fault into the application. The
application should handle this fault gracefully.
# DESCRIPTION END
| shim_verifier.dll 1 | 0 shim_verifier.dll 0'filesys.exe - 4:00:55 AM