[jbosstools-issues] [JBoss JIRA] (JBIDE-11682) Richfaces 3.3.0.Beta1 and later: Java reference search hangs
[
https://issues.jboss.org/browse/JBIDE-11682?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich commented on JBIDE-11682:
-----------------------------------------------
It looks like an out of memory case. The exception is not thrown yet, but when VM reaches
memory limits, sometimes it dies hard and long. Xmx1500m may be not enough for 50 large
projects. This is related to https://issues.jboss.org/browse/JBIDE-11539, in cached page
context we kept reference to the document object. Actually, the fix to JBIDE-11539 (for
Beta3) may fix this problem too.
There may be other contributing factors. For a project that is not a Faceted project,
WTP's validation framework does not filter out resources from derived folders (Java
output, Maven target, etc.) and we accept all resources accepted by WTP. Even for a
faceted project, Maven target might not be filtered out. Depending on a project, that may
double or even triple the memory load. We will fix that.
Richfaces 3.3.0.Beta1 and later: Java reference search hangs
------------------------------------------------------------
Key: JBIDE-11682
URL: https://issues.jboss.org/browse/JBIDE-11682
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.Beta1
Environment: Verfied on Mac OS X 10.6/10.7 and Windows XP/7; Eclipse J2EE 3.7,
SpringSource Tools Suite 2.9.0, 2.9.1; JBoss Tools Richfaces plugin 3.3.0.Beta1 and later,
including the nightly build (Apr 23rd.)
The problem does NOT occur on version 3.3.0.M5 of the Richfaces plugin.
Reporter: Alessandro Colomba
Assignee: Viacheslav Kabanovich
Labels: richfaces
Fix For: 3.3.0.CR1
Attachments: search-hung-2.txt, search-hung.txt
Given a vanilla install of Eclipse/STS on either Mac/Windows plus the Richfaces plugin, a
Java reference search (cmd/ctrl-shift-g) on a method results in:
- The method references being found and displayed in the Search pane
- The search continuing indefinitely, slowly allocating memory until the heap is
exhausted.
A stack dump of the process is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira