![]() We do not lose the pointer, we lose what it is pointing to. ![]() Sizeof(void*) is 4 on most win32 platforms, so why focus on 4 bytes? Tell me which leak would be the most painful: Or the handle is an index of a table of opaque structures or such. Okay, I hope my answer will sharpen your look at the topic: You're right - at the surface, a file handle is just a pointer to an opaque structure, deep inside the File System Driver (FSD). Why is a file handle (pointer, 4 bytes) more annoying than a memory leak? But "free list fragmentation" is improved with WinCE 6 and is anyway beyond the scope of my article. Not only memory Leaks, which obviously drain free memory from your "always to less" RAM, also other leaks like Handles itself, open files and so on make faulty applications behave fat and slow.įinally, the so called "free list fragmentation" makes Windows CE devices sometimes unusable, even if all resources are freed. But on Windows CE or Windows Mobile devices, with limited resources compared to a desktop system, the pain is much stronger. ( Note: This article deals with alpha 0.06 or higher of project.) Download source and vcproj tarball /wo crtdbg4wince - 14.7 KB.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |