This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When I am hunting memory leaks it isn't always obvious which line of code is triggering the leak. You might think that the method names of the stack-trace would be enough but if StringBuilder.append() is called then this is simply not enough. Why doesn't Netbeans include line number in the Allocation Stack Traces? When I right click and "Go to Source" it should take me to the exact line number instead of just to the method header.