Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343081 - Memory leak in Maven Pom Editor
Summary: Memory leak in Maven Pom Editor
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Milos Kleint CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-17 18:29 EDT by Snjezana Peco CLA
Modified: 2021-04-19 13:23 EDT (History)
2 users (show)

See Also:


Attachments
0001-M2e-Performance-Pom-Editor-leak (5.80 KB, patch)
2011-04-17 18:30 EDT, Snjezana Peco CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Snjezana Peco CLA 2011-04-17 18:29:48 EDT
Build Identifier: 

The Maven Pom Editor has a huge memory leak. Just opening/closing
jboss-as-parent/pom.xml causes the JVM heap to increase in size by 2-10MB
which can cause Eclipse to crash (OOM).

The leak happens when clicking the Effective POM tab. M2eclipse calls
effectivePomSourcePage.setInput(editorInput) every time when clicking this tab.
Calling StructuredTextEditor.setInput the second time adds a selection change
listener that isn't released which retains the complete MavenPomEditor
structure in the heap. The patch changes the contents of the Effective POM page
using the IDocument interface.

Patch: 0001-M2e-Performance-Pom-Editor-Leak.patch

See bug #342903


Reproducible: Always

Steps to Reproduce:
1. open some pom.xml file using the Maven Pom Editor
2. click the Effective POM tab
If you repeat these steps, you will see that the JVM heap size is continuously increasing.
Comment 1 Snjezana Peco CLA 2011-04-17 18:30:22 EDT
Created attachment 193452 [details]
0001-M2e-Performance-Pom-Editor-leak
Comment 3 Denis Roy CLA 2021-04-19 13:23:24 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/