Confirmed users
1,345
edits
Performance:Leak Tools: Difference between revisions
Jump to navigation
Jump to search
→Strategy for finding leaks
Nnethercote (talk | contribs) (→Purify) |
Nnethercote (talk | contribs) |
||
| Line 9: | Line 9: | ||
For example, start with bringing up the mail window and closing the window without doing anything. Then go on to selecting a folder, then selecting a message, and then other activities one does while reading mail. | For example, start with bringing up the mail window and closing the window without doing anything. Then go on to selecting a folder, then selecting a message, and then other activities one does while reading mail. | ||
Once you've done this, and it doesn't leak much, then try the action under trace-malloc or | Once you've done this, and it doesn't leak much, then try the action under trace-malloc or LSAN or Valgrind to find the leaks of smaller graphs of objects. (When I refer to the size of a graph of objects, I'm referring to the number of objects, not the size in bytes. Leaking many copies of a string could be a very large leak, but the object graphs are small and easy to identify using GC-based leak detection.) | ||
== What leak tools do we have? == | == What leak tools do we have? == | ||