Stm32CubeIDE crashes on startup: "Java" is not responding

[BRobe.1641]

My linux laptop (Ubuntu 22.04) failed to properly 'sleep' overnight - there is something wrong with the install of Ubuntu on my laptop. At the time, CubeIDE 1.11.2 was running, with Devstyle plugin (which has itself caused problems for me in the past). I have tried removing the 'st' folder in /opt, and reinstalling, and that had no impact. While this may just be a problem with my system76 linux laptop, other applications appear to be functioning normally.

To clarify, when I load STM32CubeIDE, the devstyle splash screen came up, and then after I proceed into the IDE, it freezes, with a message that says "Java" is not responding. On starting up since, I have skipped the devstyle splash screen, and instead get the blue-colored splash of CubeIDE - but it just freezes, saying the same thing, and suggesting I force quit.

Is there a way to diagnose this problem?

[Semer CHERNI]

Hello @BRobe.1641​ 

First let me thank you for posting.

Could you share the .log file found under the workspace_name\.metadata.

Thanks,

Semer.

[BRobe.1641]

I'm sorry for not responding - I did not see that there was a response. I ended up wiping ubuntu altogether, reinstalling, and then reinstalling Cube IDE. Then the laptop powered down in a similar way to that described above, and I now cannot load the IDE at all. Here is the .log file:

!SESSION 2023-01-28 16:26:45.510 -----------------------------------------------
eclipse.buildId=Version 1.11.2
java.version=11.0.16
java.vendor=Eclipse Adoptium
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86_64
 
!ENTRY com.st.stm32cube.ide.mcu.informationcenter 4 4 2023-01-28 16:26:51.982
!MESSAGE CubeMX plugin appears to be active, Log4j initialization might be too late.
 
!ENTRY com.st.stm32cube.ide.mcu.informationcenter 1 1 2023-01-28 16:26:52.015
!MESSAGE Log4j initialized with config file /home/baldwinrobertson/STM32CubeIDE/workspace_1.11.2/.metadata/.log4j.xml
 
!ENTRY com.st.stm32cube.ide.mcu.ide 1 1 2023-01-28 16:26:55.827
!MESSAGE Started RMI Server, listening on port 41337
 
!ENTRY org.eclipse.cdt.core 1 0 2023-01-28 16:40:31.001
!MESSAGE Indexed 'stm32h7a3iit6q_test' (0 sources, 0 headers) in 0.001 sec: 0 declarations; 0 references; 0 unresolved inclusions; 0 syntax errors; 0 unresolved names (0%)
 
!ENTRY org.eclipse.cdt.core 1 0 2023-01-28 16:45:39.118
!MESSAGE Indexed 'stm32ha7_test' (0 sources, 0 headers) in 0 sec: 0 declarations; 0 references; 0 unresolved inclusions; 0 syntax errors; 0 unresolved names (0%)
 
!ENTRY org.eclipse.cdt.core 1 0 2023-01-28 16:45:43.600
!MESSAGE Indexed 'stm32ha7_test' (24 sources, 85 headers) in 2.77 sec: 7,598 declarations; 54,691 references; 0 unresolved inclusions; 1 syntax errors; 2 unresolved names (0.0032%)
 
!ENTRY org.eclipse.cdt.core 1 0 2023-02-04 10:22:39.887
!MESSAGE Indexed 'LCD_Clock' (17 sources, 78 headers) in 1.08 sec: 3,631 declarations; 13,054 references; 0 unresolved inclusions; 1 syntax errors; 2 unresolved names (0.012%)
 
!ENTRY org.eclipse.cdt.core 1 0 2023-02-04 10:27:09.162
!MESSAGE Indexed 'LCD_Clock' (17 sources, 78 headers) in 0.823 sec: 3,642 declarations; 13,168 references; 0 unresolved inclusions; 1 syntax errors; 2 unresolved names (0.012%)
!SESSION 2023-03-05 13:04:19.554 -----------------------------------------------
eclipse.buildId=Version 1.11.2
java.version=11.0.16
java.vendor=Eclipse Adoptium
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86_64
 
!ENTRY org.eclipse.core.resources 2 10035 2023-03-05 13:04:40.818
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
 
!ENTRY com.st.stm32cube.ide.mcu.informationcenter 4 4 2023-03-05 13:04:42.669
!MESSAGE CubeMX plugin appears to be active, Log4j initialization might be too late.
 
!ENTRY com.st.stm32cube.ide.mcu.informationcenter 1 1 2023-03-05 13:04:42.706
!MESSAGE Log4j initialized with config file /home/baldwinrobertson/STM32CubeIDE/workspace_1.11.2/.metadata/.log4j.xml
!SESSION 2023-03-05 13:05:18.578 -----------------------------------------------
eclipse.buildId=Version 1.11.2
java.version=11.0.16
java.vendor=Eclipse Adoptium
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86_64
 
!ENTRY org.eclipse.core.resources 2 10035 2023-03-05 13:05:19.748
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
 
!ENTRY com.st.stm32cube.ide.mcu.informationcenter 4 4 2023-03-05 13:05:21.720
!MESSAGE CubeMX plugin appears to be active, Log4j initialization might be too late.
 
!ENTRY com.st.stm32cube.ide.mcu.informationcenter 1 1 2023-03-05 13:05:21.757
!MESSAGE Log4j initialized with config file /home/baldwinrobertson/STM32CubeIDE/workspace_1.11.2/.metadata/.log4j.xml
!SESSION 2023-03-05 13:07:40.961 -----------------------------------------------
eclipse.buildId=Version 1.11.2
java.version=11.0.16
java.vendor=Eclipse Adoptium
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86_64
 
!ENTRY org.eclipse.core.resources 2 10035 2023-03-05 13:07:42.415
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
 
!ENTRY com.st.stm32cube.ide.mcu.informationcenter 4 4 2023-03-05 13:07:44.404
!MESSAGE CubeMX plugin appears to be active, Log4j initialization might be too late.
 
!ENTRY com.st.stm32cube.ide.mcu.informationcenter 1 1 2023-03-05 13:07:44.450
!MESSAGE Log4j initialized with config file /home/baldwinrobertson/STM32CubeIDE/workspace_1.11.2/.metadata/.log4j.xml
!SESSION 2023-03-05 13:09:52.769 -----------------------------------------------
eclipse.buildId=Version 1.11.2
java.version=11.0.16
java.vendor=Eclipse Adoptium
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86_64
 
!ENTRY org.eclipse.core.resources 2 10035 2023-03-05 13:09:53.789
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
 
!ENTRY com.st.stm32cube.ide.mcu.informationcenter 4 4 2023-03-05 13:09:55.535
!MESSAGE CubeMX plugin appears to be active, Log4j initialization might be too late.
 
!ENTRY com.st.stm32cube.ide.mcu.informationcenter 1 1 2023-03-05 13:09:55.571
!MESSAGE Log4j initialized with config file /home/baldwinrobertson/STM32CubeIDE/workspace_1.11.2/.metadata/.log4j.xml

[BRobe.1641]

Also, I think I found where the executable for STM32CubeIDE is installed (/opt/st/stm32cubeide_1.11.2), but when I execute it from the command line, i.e.:

/opt/st/stm32cubeide_1.11.2$ ./stm32cubeide

I get an error, as follows:

Please choose another workspace, as [workspace folder location] is currently in use. RETRY/CHOOSE

Is it possible that my laptop powered down improperly, while I had left STM32Cube running, and so it is causing this error?

[cit]

For me renaming (removing) the .metadata/.lock file did the trick. HTH

LE: Actually, I ended up renaming the .metadata altogether (following the advice of someone else in this thread) and copying the missing .plugins/ directory contents from the old renamed .metadata to the newly generated .metadata/.plugins directory.

[HackyJ]

Have the same issue after closing the laptop before ending the stm32cubeide_1.12 finally.

at startup this morning, even after a restart of linux, the ide locks up with java did not answer.

I the started a second instance of stm32cubeide which requested a new workspace.

With this workspace it works. Seems something in the workspace gets damaged on hibernate.

[HackyJ]

Added the damaged workspace for analysis.

[LLope.31]

Hello, I had this problem, where my IDE wouldnt open, and give the "java not responding" error after about 2 minutes of waiting. I was able to open the IDE again by deleting the .metadata folder in my workspace. Everything seems to be working now, I just needed to open the workspace directory again. Some configurations seem to have reverted back.

I hope this helps

[danimal1802]

Removing the .metadata directory works for me.   I am running on Ubuntu 22.x Desktop with the STM32CubeIDE v 1.144.0.   Additionally, I am running this on a Proxmox virtual machine with a virtual USB port mapped to a physical port.  

[iso9660]

It also worked for me

[IAnan.3]

I have the same problem. But the difference is that I use ubuntu 23.04.

[shane mattner]

I ran into this same problem today running Fedora 38 on a Thinkpad Carbon X1.  I was able to start CubeIDE only if the workspace was pointed toward the default location.  For me that workspace path is /home/shane/STM32CubeIDE/workspace_1.12.1

After changing the workspace path I was able to create new projects, build, and debug as normal.

Update: I ran into this problem again on Ubuntu 22.04 and v1.12.1 of CubeIDE.  I removed `/opt/st/stm32cubeide_1.12.1/` and installed v1.13.1.  Cube is working now.

[rybanu]

in my case :

1  copy folder metadata(hidden folder in workspace ) to enother place , delete folder metadata in workspace

2 run CUBEIDE . (system created new metadata) 

3  copy   old folder  plugins (from  .metadata/.plugins)   , to your new folder metadata without  folder org.eclipse.e4.workbench  ...   ITS work for me and ceep all settings 

 

[PGump.1]

Hi,

I have had this problem many times, for various reasons. I'm running Linux Suse - Tumbleweed.

I have found deleting the .metadata directory doesn't always work.

What always works for me is -

• Rename the workspace folder, create a new folder with the old name.
• Start CubeIDE and open the new workplace folder.
• DON"T use the Import Project on the home page.
• Use File > Import > Existing Project into Workspace. Browse for the old folder, select projects. Select Copy Projects into Workspace.
• When prompted to Reset project settings - select Yes to all...

I hope this helps.

Kind regards
Pedro