|
From: John R.
|
Bryan Meredith wrote: > What would be a good way to approach the project team as "your stuff > leaks here - my experimental tool says so (and so does this one)" is > probably not going to make me any friends... Perhaps they would be convinced by a simple test program (preferably short, too) that contains a loop which triggers the leak over and over. Use the "VIRT" column of the output from /usr/bin/top , or the "SZ" column of the output from "ps -l" to show that the process size is increasing when it should not. Then give them the patch that fixes the leak, and run the test program again, observing no increase in size. Wait until they ask, "Neat. How did you find the leak?" -- |