Memory Growth and CMap

0 Likes

Problem:

My application uses CMap objects extensively, and I am observing continuous memory growth in the task manager, but BoundsChecker does not report a leak.  Is BoundsChecker missing something?

Resolution:

Any time you manipulate a CMap object, whether adding items or simply sorting or rearranging them, it creates additional node objects. These don't get leaked, but they are not deleted until the entire CMap object is destroyed, or all elements are cleared. Over time, this can eat up substantial memory if the CMap is being manipulated frequently, but since the nodes are not leaked, BoundsChecker does not flag an error.

Old KB# 12332
Comment List
Anonymous
Related Discussions
Recommended