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

Bug 84244

Summary:	Memory leaks in JSP editor
Product:	[WebTools] WTP Source Editing	Reporter:	Andrey Loskutov <loskutov>
Component:	jst.jsp	Assignee:	jst.jsp <jst.jsp-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Andrey Loskutov

2005-02-02 12:24:14 EST

As long time user ;) of first IBM WTP contribution, then of Milestone 2 from WTP 
I saw always the very big problem with WTP/Structured Editors (for HTML and JSP) 
- they have (multiple?) memory leaks, particularly on copy/paste and search/
replace operations. After long time editing jsp's Eclipse memory consumption 
constantly increases and does not decrease after closing jsp editors. The "same" 
kind of operations with Java editor doesn't causes such strong memory usage.

I have read about similar bug 82608, but in our JSP's we don't use any tag's so 
the memory problem should be still there.

Is it also possible to add some extra test cases which could trace memory usage 
after continuous find/replace and copy/paste actions in WTP editors, and also 
before/after continuous open/close jsp editors?

I'm using both Eclipse 3.0 and 3.1 with initial IBM distribution and with WTP 
M2, with JDK 1.4.2 on WinXp.

Comment 1 Phillip Avery

2005-06-16 00:37:23 EDT

I'm assuming fixed with these other JSP memory fixes.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=95960

*** This bug has been marked as a duplicate of 95960 ***

Comment 2 David Williams

2005-07-25 11:38:42 EDT

Marking as verified as I know this issue is fixed (or correctly categorized).
If, as originator, you disagree or still see, please re-open, or open a new bug. 

Thanks very much for reporting and helping make our JSP editing better.

Comment 3 John Lanuti

2006-11-28 15:38:57 EST

This is part of a mass update to close out all stale WTP defects already verified by the reporter but awaiting closure by the assignee.  If you feel this defect was closed inappropriately, please reopen.

Thanks, John Lanuti