No, I am quite sure thats not how it is supposed to look, but it is how it does look ! Either fix it or get used to it.
If the leak in in the 'main' function, bad luck ! Or a method called directly by LCL. But in most cases of a leak, its in a method that has been called from your own code, and therefore the report is far easy to read.
It is simply borked, and if that output is actually what should be outputted then it is broken by design (not to add completely useless for real world situations).
Rubbish. As I said, its not great but it is usually quite functional. I have been using it like that for years, and I have written a lot of leaky code ! But I never failed to find the leak. I always assumed every one only saw the calling method. Quite surprised that windows user get more specific information, good for them !
Here is a simple rule to avoid this problem, when you write leaky code, make sure its in a function or procedure that is called by your own code ! Easy...
Davo