Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 335975

Summary:	Apparent memory leak in GDB Traces console
Product:	[Tools] CDT	Reporter:	Marc Dumais <marc.dumais>
Component:	cdt-debug-dsf-gdb	Assignee:	Project Inbox <cdt-debug-dsf-gdb-inbox>
Status:	NEW ---	QA Contact:	Jonah Graham <jonah>
Severity:	normal
Priority:	P3	CC:	cdtdoug, marc.dumais, pawel.1.piech, sunehh
Version:	8.0
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Marc Dumais

2011-02-01 10:38:02 EST

Build Identifier: M20100909-0800

When doing activity that generates output to the GDB Tracing console, memory usage grows as more output is added to the console.   

If one clears the console (using the "clear console" button while the GDB Traces console is selected/active), the memory is freed, as expected.

But if one instead kills the DSF-GDB session and uses the "Remove all Terminated Launches" button, the memory seems to stay allocated.

The object type that seems to be leaking, as seen in VisualVM, is :  org.eclipse.jface.text.TreeLineTracker$Node .   



Reproducible: Always

Steps to Reproduce:
1. Start VisualVM, and select eclipse as profiling target.  Optional: use "TreeLine" as filter to only see the objects of the type that seems to be leaking.
2. Start a DSF-GDB post-mortem debugging session.  Do something to generate output on the GDB Traces console, like navigating the tracepoint frames.
3. Observe that objects of type "org.eclipse.jface.text.TreeLineTracker$Node" are allocated, as the console grows.
4. Terminate the launch.   Click on the "Remove all Terminated Launches" button.
5. Observe that the objects previously described stay allocated for the most part.