Bugzilla

leakcheck prints out a list of classes that are leaked. It orders the list in alphabetical order, and prints out the first half dozen of them. This is fine for small leaks that only include a few things, but with larger leaks the classes are fairly useless.

Two problems with this are:
* In bug 1569708 comment 43, kats complains that "APZ gets blamed for all these leaks because the objects are listed in alphabetical order" and classes like APZEventState are often at the front.
* It makes it harder to tell that different leaks might be the same. If a class is added, removed or renamed and is near the start of the alphabet, then the "signature" will change for the purpose of TreeHerder starring. It can also make the same leak look different on different platforms. I saw a case recently where the Windows version of the leak had Direct3D as one of the leaked objects, whereas of course the Linux version did not.
* It makes it harder to assess the severity of a leak. A leak that involves a DOM window or document is usually worse than one that just involves some network channels that didn't get torn down properly at shutdown.

I'm not sure what the best way to improve this situation. I was thinking there could be a whitelist of important classes. The list of leaked classes would be filtered, and if that found any then you'd use that list (alphabetized as usual).

leakcheck prints out a list of classes that are leaked. It orders the list in alphabetical order, and prints out the first half dozen of them. This is fine for small leaks that only include a few things, but with larger leaks the classes are fairly useless.

Two problems with this are:
* In bug 1569708 comment 43, kats complains that "APZ gets blamed for all these leaks because the objects are listed in alphabetical order" and classes like APZEventState are often at the front.
* It makes it harder to tell that different leaks might be the same. If a class is added, removed or renamed and is near the start of the alphabet, then the "signature" will change for the purpose of TreeHerder starring. It can also make the same leak look different on different platforms. I saw a case recently where the Windows version of the leak had Direct3D as one of the leaked objects, whereas of course the Linux version did not.
* It makes it harder to assess the severity of a leak. A leak that involves a DOM window or document is usually worse than one that just involves some network channels that didn't get torn down properly at shutdown.

I'm not sure what the best way to improve this situation. I was thinking there could be an allow list of important classes. The list of leaked classes would be filtered, and if that found any then you'd use that list (alphabetized as usual).