485
edits
Using dfSplat to identify object leaks: Difference between revisions
Using dfSplat to identify object leaks (view source)
Revision as of 16:04, 24 March 2020
, 24 March 2020Not 11 but 10 (details are important)
m (more spelling etc..) |
m (Not 11 but 10 (details are important)) |
||
| Line 37: | Line 37: | ||
As you can see we are creating 21 objects based on the cObject class and store the object ID's in Objects array. | As you can see we are creating 21 objects based on the cObject class and store the object ID's in Objects array. | ||
Then there's some code we are not showing where the objects are used for whatever and finally we destroy the objects. | Then there's some code we are not showing where the objects are used for whatever and finally we destroy the objects. | ||
But.. we only destroy objects with an even object ID, so we are leaking | But.. we only destroy objects with an even object ID, so we are leaking 10 objects on purpose here to display how it works. | ||
=== How to run the application in dfSplat === | === How to run the application in dfSplat === | ||