Memory leak compile error: Difference between revisions
Jump to navigation
Jump to search
Thunder4ik (talk | contribs) m (→See also: Unicodifying, replaced: See Also → See also) |
m (Nesciuse moved page Memory leak compile error/en to Memory leak compile error without leaving a redirect: Move en subpage to basepage) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{ | {{LanguageBar}} | ||
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. | ||
| Line 5: | Line 6: | ||
==See also== | ==See also== | ||
* [[Memory Leak Fixes]] | * [[Memory Leak Fixes]] | ||
[[Category:Level Design FAQ]] | |||
[[Category:Compile Errors]] | |||
Latest revision as of 08:21, 12 July 2024
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.