[
https://issues.jboss.org/browse/JBIDE-11682?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich commented on JBIDE-11682:
-----------------------------------------------
If your workspace contains 50 interdependent project with 1000 xhtmls, then the search
looks into each of these 1000 files, it requests xml documents for them (now not to be
cached), scans each node and attribute for EL instances, and caches results into objects
to be used at next searches. That still takes time and memory. Your new stack traces do
not imply hanging, but just great volume of work. Could you please try waiting for
completion of the search job couple times with -Xms2000m and -Xms2500m and let us know how
long it took? (If the waiting time is unreasonably long, say >15min, then of course
stop waiting, and let us know of the limit.)
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-nightly-201204030-1.txt,
search-hung-nightly-201204030-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