Lines Matching full:objects

7 with the difference that the orphan objects are not freed but only
17 number of new unreferenced objects found. If the ``debugfs`` isn't already
37 Note that the orphan objects are listed in the order they were allocated
39 objects to be reported as orphan.
61     marking all current reported unreferenced objects grey,
62     or free all kmemleak objects if kmemleak has been disabled.
99   1. mark all objects as white (remaining white objects will later be
105   3. scan the gray objects for matching addresses (some white objects
108   4. the remaining white objects are considered orphan and reported via
123 'clear' command to clear all reported unreferenced objects from the
125 you can find new unreferenced objects; this should help with testing
138 Freeing kmemleak internal objects
142 disabled by the user or due to an fatal error, internal kmemleak objects
143 won't be freed when kmemleak is disabled, and those objects may occupy
182 The false negatives are real memory leaks (orphan objects) but not
184 point to such objects. To reduce the number of false negatives, kmemleak
189 The false positives are objects wrongly reported as being memory leaks
190 (orphan). For objects known not to be leaks, kmemleak provides the