[jbosstools-issues] [JBoss JIRA] (JBIDE-11682) Richfaces 3.3.0.Beta1 and later: Java reference search hangs

[Alexey Kazakov (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688208#comment-12688208 ] 

Alexey Kazakov commented on JBIDE-11682:
----------------------------------------

How many XHTML/HTML/XML files do you have in your projects? It could take some time to search java references in such files first time if there are many of them. We fixed the problem with memory consumption (see JBIDE-11539 ) for Beta3 but anyway how many memory did you allow to use to your eclipse? What do you have in eclipse.ini?
                
> 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, 3.3.0.Beta2
>         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: Alexey Kazakov
>              Labels: richfaces
>         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