Java.lang.StackOverflowError when creating a Sencha / ExtJS 5 project

Question

When I open my project and Eclipse tries to create it, I get this error: An internal error occurred during: "Building workspace". java.lang.StackOverflowError.

He is still finishing construction (I think), and I can continue. But I get an “Internal Error” pop-up that says that the stack overflowed and that I decided to exit the workplace. I just ignore the popup.

Here is my .log output:

!SESSION 2014-11-13 09:22:21.634 ----------------------------------------------- eclipse.buildId=4.4.0.I20140606-1215 java.version=1.7.0_51 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product -data C:\Workspaces\pvmui-ws3 !ENTRY org.eclipse.egit.ui 2 0 2014-11-13 09:22:31.052 !MESSAGE Warning: EGit couldn't detect the installation path "gitPrefix" of native Git. Hence EGit can't respect system level Git settings which might be configured in ${gitPrefix}/etc/gitconfig under the native Git installation directory. The most important of these settings is core.autocrlf. Git for Windows by default sets this parameter to true in this system level configuration. The Git installation location can be configured on the Team > Git > Configuration preference page 'System Settings' tab. This warning can be switched off on the Team > Git > Confirmations and Warnings preference page. !ENTRY org.eclipse.egit.ui 2 0 2014-11-13 09:22:31.057 !MESSAGE Warning: The environment variable HOME is not set. The following directory will be used to store the Git user global configuration and to define the default location to store repositories: 'C:\Users\XXXXXX'. If this is not correct please set the HOME environment variable and restart Eclipse. Otherwise Git for Windows and EGit might behave differently since they see different configuration options. This warning can be switched off on the Team > Git > Confirmations and Warnings preference page. !ENTRY org.eclipse.core.jobs 4 2 2014-11-13 09:24:25.196 !MESSAGE An internal error occurred during: "Building workspace". !STACK 0 java.lang.StackOverflowError at org.eclipse.vjet.dsf.jst.declaration.JstProxyType.getName(JstProxyType.java:105) at org.eclipse.vjet.dsf.jst.declaration.JstMixedType.getName(JstMixedType.java:75) **THESE TWO LINES REPEAT ABOUT 1023 TIMES** !ENTRY org.eclipse.vjet.eclipse.core 4 0 2014-11-13 09:24:26.431 !MESSAGE There is no jst2dltk translator for node: org.eclipse.vjet.dsf.jst.term.ObjLiteral !ENTRY org.eclipse.vjet.eclipse.core 4 0 2014-11-13 09:24:26.510 !MESSAGE There is no jst2dltk translator for node: org.eclipse.vjet.dsf.jst.term.ObjLiteral !ENTRY org.eclipse.ui 4 4 2014-11-13 09:24:27.036 !MESSAGE Conflicting handlers for org.eclipse.vjet.eclipse.debug.ui.launchShortcut.run: {org.eclipse.debug.internal.ui.la unchConfigurations.LaunchShortcutExtension$LaunchCommandHandler@ 6436afd6} vs {org.eclipse.debug.internal.ui.la unchConfigurations.LaunchShortcutExtension$LaunchCommandHandler@ 42523e00} 

What to do to avoid this problem?

Answer 1

JstMixedType seems to accumulate several types and concatenate their names. In your case, it contains itself (or a proxy server around itself, it says for sure). It should not be. This is similar to a bug in the VJET core and should be reported .

Perhaps you can get around the error by adapting your configuration / code. Do you have mixed types that contain themselves? Is this intended? (perhaps it is) If not, change them.

Answer 2

How to work with StackOverflowError:

The simplest solution is to carefully check the stack trace and detect a duplicate line number pattern. These line numbers indicate that the code is called recursively. When you find these lines, you should carefully check your code and understand why the recursion never ends.

---

If you have confirmed the implementation of the recursion is correct, you can increase the size of the stacks to allow more calls. Depending on the installed Java Virtual Machine (JVM), the default stack size can be either 512 KB or 1 MB. You can increase the size of the thread stack with the -Xss flag. This flag can be specified either through the configuration of projects, or through the command line. The format of the -Xss argument -Xss :

 -Xss<size>[g|G|m|M|k|K] 

By the way, this seems to be an eclipse bug (read this ref ), which has been fixed in the latest version.