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

Mon Apr 30 13:32:18 EDT 2012

     [ https://issues.jboss.org/browse/JBIDE-11682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessandro Colomba updated JBIDE-11682:
---------------------------------------

    Attachment: search-hung-nightly-201204030-1.txt
                search-hung-nightly-201204030-2.txt

I'm afraid the Apr 30th 2012 snapshot did not fix the problem. However unlike the previous snapshot, I'm now able to exit Eclipse normally instead of having to kill the process.

I'm attaching two new stack traces in case it might help.

> 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