Memory leak compile error: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
[[Category: | [[Category:Level Design FAQ]] | ||
The error message "<code>"Memory leak: mempool blocks left in memory: ''<number>''</code>" is harmless -- you can safely ignore it. | The error message "<code>"Memory leak: mempool blocks left in memory: ''<number>''</code>" is harmless -- you can safely ignore it. | ||
Note that this has nothing to do with [[Leaks Explained|level leaks]]. The error originates from the CMemoryPool utility class. It's also important to note that after the message is printed, the memory pool is cleared. | Note that this has nothing to do with [[Leaks Explained|level leaks]]. The error originates from the CMemoryPool utility class. It's also important to note that after the message is printed, the memory pool is cleared. |
Revision as of 20:20, 21 January 2006
The error message ""Memory leak: mempool blocks left in memory: <number>
" is harmless -- you can safely ignore it.
Note that this has nothing to do with level leaks. The error originates from the CMemoryPool utility class. It's also important to note that after the message is printed, the memory pool is cleared.