]
Snjezana Peco commented on JBIDE-1896:
--------------------------------------
The JBDS259a.zip patch fixes the issue described in this jira. Maxim has committed this
patch.
JBIDE-1896.zip even fixes some additional memory leaks. I have committed it.
The memory leak described in note 6 is a webtools bug. The fix for it isn't committed.
I talked to Max about it and he decided to skip that fix and enter a bug into the webtools
project.
There are some more memory leaks that aren't related to this jira and aren't so
extensive.
JBDS1.0 Massive Memory Leak using JBoss Tool HTML Editor on .XHTML
files
------------------------------------------------------------------------
Key: JBIDE-1896
URL:
http://jira.jboss.com/jira/browse/JBIDE-1896
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 2.0.0.GA
Environment: * Windows XP Professional
* Fresh installation of JBDS 1.0, no additional plugins/features updates etc.
* Working from a freshly seam-gen generated project
Reporter: Andy Conn
Assigned To: Snjezana Peco
Priority: Critical
Fix For: 2.2.x
Attachments: display.xhtml, edit.xhtml, JBDS259.zip, JBDS259a.zip,
JBIDE-1896.zip, menu.xhtml, NewPartDetail.xhtml, template.xhtml, test.xhtml,
testdiv.xhtml
Please refer to the disucssion @
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134003#...
Original Post:
There seems to be a major memory leak making the JBoss HTML Editor completely unusable.
Mem usage in Task Manager shows as follows:
* 111,448 On a fresh open of Jboss Dev Studio
* 189,144 Opening an .xhtml file (in visual/source mode) using in the "Jboss HTML
Editor"
* 197,932 Removed a blank line from the source & saved
* 207,180 Inserted a blank line in source & saved
* 211,168 Inserted a space in source & saved
* 357,392 Inserted & Deleted a blank line in source: repeat 20x (no saves in
between)
Clearly there is some dramatic memory problem here.
Note:
1) The problem does not seem to occur when mode is set to "Source"
2) The memory is not released even if the HTML Editor is closed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: