[jbosstools-issues] [JBoss JIRA] (JBIDE-16689) Crash after CTRL + rightclick + find implementation

[Victor Rubezhny (JIRA)]

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

Victor Rubezhny edited comment on JBIDE-16689 at 3/7/14 12:08 PM:
------------------------------------------------------------------

[~velteyn], 

I can reproduce Marco's exception on JBDS 6.0.1 (installed from jbdevstudio-product-eap-universal-6.0.1.GA-v20130327-2052-B361.jar). So, yes JSDT Core (that comes from WTP v.3.4.2) has an issue, and that issue is fixed in latest version of JSDT Core. In short, JSDT Core doesn't catch SelectionNodeFound Exception while it should catch this exception for its proper work. In your case this means that Hover probably will not be shown for your method. (It's not about 'find declaration', but it's about a hover that is to be shown when you're holding your mouse cursor for a second or two over some variable or function in the editor. It often is displayed at the moment when you are opening a ctrl-rc context menu, just by an occasion.)
But this exception is not a fatal error, so it shouldn't lead to exiting from JBDS. We can provide you with a fixed version of org.eclipse.wst.jdbs.core, but IMHO it will not solve your initial 'crash' situation.

IMHO, there are some other reasons for JBDS to be exited. For example, an OutOfMemory exception (I didn't see such an exception in your logs, but you provided a truncated log only, so it might be there). Some features of JDBS (and particulary JSDT) are very demanding in terms of memory. 64-bit applications require more memory to run comparing to the 32-bit ones. You wrote that your project is a big one, so probably you should tune your JBDS to use more memory. For example, you may increase the setings in your <jbds>/studio/jbdevstudio.ini:
{code}
-vmargs
-Xms512m
-Xmx1024m
{code}

Another possible reason could be an access violations in JVM. In this case you can find dump files, named like hs_err_pid<PID of JBDS>.log as I described above, in:
- JBDS installation folder
- In your home folder
The labels like "Problematic Frame" may tell you the library or executable which is probably caused the crash.

I'd started with searching for the dumps stored on your system, investigating your full .log file and increasing the memory settings for JBDS.
                
      was (Author: vrubezhny):
    [~velteyn], 

I can reproduce Marco's exception on JBDS 6.0.1 (installed from jbdevstudio-product-eap-universal-6.0.1.GA-v20130327-2052-B361.jar). So, yes JSDT Core (that comes from WTP v.3.4.2) has an issue, and that issue is fixed in latest version of JSDT Core. In short, JSDT Core doesn't catch SelectionNodeFound Exception while it should catch this exception for its proper work. In your case this means that Hover probably will not be shown for your method. (It's not about 'find declaration, but it's about a hover that is to be shown when you're holding your mouse cursor for a second or two over some variable or function in the editor. It often is displayed at the moment when you are opening a ctrl-rc context menu, just by an occasion.)
But this exception is not a fatal error, so it shouldn't lead to exiting from JBDS. We can provide you with a fixed version of org.eclipse.wst.jdbs.core, but IMHO it will not solve your initial 'crash' situation.

IMHO, there are some other reasons for JBDS to be exited. For example, an OutOfMemory exception (I didn't see such an exception in your logs, but you provided a truncated log only, so it might be there). Some features of JDBS (and particulary JSDT) are very demanding in terms of memory. 64-bit applications require more memory to run comparing to the 32-bit ones. You wrote that your project is a big one, so probably you should tune your JBDS to use more memory. For example, you may increase the setings in your <jbds>/studio/jbdevstudio.ini:
{code}
-vmargs
-Xms512m
-Xmx1024m
{code}

Another possible reason could be an access violations in JVM. In this case you can find dump files, named like hs_err_pid<PID of JBDS>.log as I described above, in:
- JBDS installation folder
- In your home folder
The labels like "Problematic Frame" may tell you the library or executable which is probably caused the crash.

I'd started with searching for the dumps stored on your system, investigating your full .log file and increasing the memory settings for JBDS.
                  
> Crash after CTRL + rightclick + find implementation
> ---------------------------------------------------
>
>                 Key: JBIDE-16689
>                 URL: https://issues.jboss.org/browse/JBIDE-16689
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: upstream
>            Reporter: Edoardo Barolo
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira