Bug 241383 - Memory Rendering leaks memory during scroll
Summary: Memory Rendering leaks memory during scroll
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-memory (show other bugs)
Version: 6.0   Edit
Hardware: PC Linux-GTK
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-18 08:17 EDT by James Blackburn CLA
Modified: 2020-09-04 15:24 EDT (History)
2 users (show)

See Also:

Attachments
screenshot of heap dump (260.32 KB, image/png)
2008-07-18 08:18 EDT, James Blackburn CLA 		no flags Details
Turn populateCache asyncExec -> syncExec (1023 bytes, patch)
2008-07-18 08:28 EDT, James Blackburn CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James Blackburn CLA 2008-07-18 08:17:16 EDT 
Build ID: 3.4.0

Steps To Reproduce:
Just updated my checkout of Memory Renderings to today's HEAD.  First time i used it, I got a out of memory error.

Examining the heap in Eclipse memory analyzer showed ~280M of memory being consumed by TraditionalMemoryByte (see attached screenshot).

It looks like the culprit is the TraditionalMemoryByte[] being held around while the display runnable waits to exec.
Comment 1 James Blackburn CLA 2008-07-18 08:18:01 EDT 
Created attachment 107819 [details]
screenshot of heap dump
Comment 2 James Blackburn CLA 2008-07-18 08:28:11 EDT 
Created attachment 107820 [details]
Turn populateCache asyncExec -> syncExec 

Turn populateCache's asyncExec -> syncExec -- this seems to do the trick
Comment 3 James Blackburn CLA 2011-03-17 14:02:13 EDT 
Traditional Memory Rendering now lives in CDT -> moving bugs