Solved

Developer Studio 22.12 cannot start after installration


Userlevel 5
Badge +9
  • Sidekick (Employee)
  • 50 replies

Hi , today , I just download IFS Developer Studio 22.12 from https://developer.ifs.com/tools/devstudio

and installed it.

The installration itself is ok.

 

while, I cannot boot the Dev Studio after the installration.

everytime i try to boot IFS Dev Studio, it generates  “hs_err_pid11196.log”  under  C:\Program Files\IFS\DeveloperStudio22.120

and shows:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff83d5bf74a, pid=11196, tid=324
#
# JRE version: OpenJDK Runtime Environment AdoptOpenJDK (14.0.2+12) (build 14.0.2+12)
# Java VM: OpenJDK 64-Bit Client VM AdoptOpenJDK (14.0.2+12, mixed mode, compressed oops, serial gc, windows-amd64)
# Problematic frame:
# C  [awt.dll+0x8f74a]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
#   https://github.com/AdoptOpenJDK/openjdk-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

Current thread (0x0000000011367800):  JavaThread "AWT-EventQueue-0" [_thread_in_native, id=324, stack(0x00000000126f0000,0x00000000128f0000)]

Stack: [0x00000000126f0000,0x00000000128f0000],  sp=0x00000000128ee710,  free space=2041k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [awt.dll+0x8f74a]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  sun.awt.windows.WComponentPeer._setFont(Ljava/awt/Font;)V+0 java.desktop@14.0.2
j  sun.awt.windows.WComponentPeer.setFont(Ljava/awt/Font;)V+7 java.desktop@14.0.2
j  sun.awt.windows.WWindowPeer.initialize()V+42 java.desktop@14.0.2
j  sun.awt.windows.WFramePeer.initialize()V+1 java.desktop@14.0.2
j  sun.awt.windows.WComponentPeer.<init>(Ljava/awt/Component;)V+83 java.desktop@14.0.2
j  sun.awt.windows.WCanvasPeer.<init>(Ljava/awt/Component;)V+2 java.desktop@14.0.2
j  sun.awt.windows.WPanelPeer.<init>(Ljava/awt/Component;)V+2 java.desktop@14.0.2
j  sun.awt.windows.WWindowPeer.<init>(Ljava/awt/Window;)V+2 java.desktop@14.0.2
j  sun.awt.windows.WFramePeer.<init>(Ljava/awt/Frame;)V+2 java.desktop@14.0.2
j  sun.awt.windows.WToolkit.createFrame(Ljava/awt/Frame;)Ljava/awt/peer/FramePeer;+5 java.desktop@14.0.2
j  java.awt.Frame.addNotify()V+20 java.desktop@14.0.2
j  java.awt.Window.pack()V+28 java.desktop@14.0.2
j  org.netbeans.core.startup.Splash.center(Ljava/awt/Window;)V+1
j  org.netbeans.core.startup.Splash$SplashRunner.run()V+11
j  java.awt.event.InvocationEvent.dispatch()V+47 java.desktop@14.0.2
j  java.awt.EventQueue.dispatchEventImpl(Ljava/awt/AWTEvent;Ljava/lang/Object;)V+21 java.desktop@14.0.2
j  java.awt.EventQueue$4.run()Ljava/lang/Void;+32 java.desktop@14.0.2
j  java.awt.EventQueue$4.run()Ljava/lang/Object;+1 java.desktop@14.0.2
j  java.security.AccessController.executePrivileged(Ljava/security/PrivilegedAction;Ljava/security/AccessControlContext;Ljava/lang/Class;)Ljava/lang/Object;+29 java.base@14.0.2
j  java.security.AccessController.doPrivileged(Ljava/security/PrivilegedAction;Ljava/security/AccessControlContext;)Ljava/lang/Object;+13 java.base@14.0.2
j  java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Ljava/security/PrivilegedAction;Ljava/security/AccessControlContext;Ljava/security/AccessControlContext;)Ljava/lang/Object;+18 java.base@14.0.2
j  java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V+46 java.desktop@14.0.2
j  java.awt.EventDispatchThread.pumpOneEventForFilters(I)V+78 java.desktop@14.0.2
j  java.awt.EventDispatchThread.pumpEventsForFilter(ILjava/awt/Conditional;Ljava/awt/EventFilter;)V+35 java.desktop@14.0.2
j  java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V+11 java.desktop@14.0.2
j  java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4 java.desktop@14.0.2
j  java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V+3 java.desktop@14.0.2
j  java.awt.EventDispatchThread.run()V+9 java.desktop@14.0.2
v  ~StubRoutines::call_stub

siginfo: EXCEPTION_ACCESS_VIOLATION (0xc0000005), reading address 0x0000000000000058

 

icon

Best answer by Charith Epitawatta 9 May 2022, 20:54

View original

7 replies

Userlevel 5
Badge +9

I just googled the error and found that [awt.dll+0x8f74a] error usually  occours on Japanese OS.

Then I just swith my windows UI language to English , and now I can boot IFS Dev Studio.

 

So, is it a bug? and only occour on Japanese OS?

Userlevel 7
Badge +31

Hi @Shou,

In OpenJDK Bug System, there is a bug for this and it is mentioned that it is fixed in version 16 build b12. From your error message, it looks like you are using OpenJDK 14. 

If you are using the JDK that comes packaged with IFS Developer Studio, which I think you are, as the latest version of the tool is supposed to come with JDK 14, I think you can report this to R&D. Hopefully they can upgrade Developer Studio to a newer version of the JDK where this issue is fixed.

Until then, as a workaround, hope you can use English instead of Japanese in Windows.

Hope this helps!

Userlevel 5
Badge +13

Hi @Shou 

 

glad to see that you solved issue by changing the Windows UI language English from Japanese. Even though JDK 14 incompatibility issue in Japanese OS is solved in JDK version 16 as mentioned in https://bugs.openjdk.java.net/browse/JDK-8249215, we cannot change the JDK version in the latest tool as the latest  tool(22.1) is based on NetBeans 12 and it i’s compatible with JDK 14.

 

Thanks

Harshini

Userlevel 5
Badge +13

Hi @Shou 

 

As I mentioned in my previous comment, the latest Devstudio tool 22.1 is based on NetBeans 12 and it i’s compatible with JDK 14, and that is why we have packed the exe with latest JDK 14 which is tested and verified. So it’s unable for us to change the packed version in the tool.

This issue is an incompatibility issue with Open JDK 14 and Japanese OS.

Hope you will be able to try following workarounds to rectify the issue. I know you have already tried the 2nd option. and it works for you.

 

Workarounds:

  1. Try out another JDK 14 version from a different vendor ( Oracle says their JDK14 supports different locales including Japanese : link ) - Try Oracle JDK 14.
  2. Change the OS language to English (which you have already tried and working)

 

Best Regards

Harshini

Userlevel 5
Badge +9

@hamalk 

  thanks for your solution , but I have one concern regarding your solution (1)

  as you mentioned , R&D only tested aginst OpenJDK14 , so if we change JDK to Oracle JDK14.

  do we still get IFS Standard Support?

   eg,  If there is any other issue occurs , and the reason is we using Oracle JDK14,  will R&D responible for fixing the issue?

Userlevel 5
Badge +13

Hi @Shou 

 

We created an internal User story to test the tool with Oracle JDK 14 in Japanese OS. Will do some tests and let you know the outcome. For the tool we have chosen Open JDK 14 as it was recommended by NetBeans 12 to use the latest version of Open JDK 14.(jdk-14.0.2_64bit).

 

Thanks

Harshini

 

Userlevel 5
Badge +9

The Final Soluton:

1)Right Click on Desktop →[新規作成]-> [ショートカット]

2)Select IFS Developer Stuidio’s exe: 

  eg: C:\Program Files\IFS\DeveloperStudio22.12\bin\developer_studio64.exe

      then Create the  Shortcut

3)Right Click on the shortcut → [プロパティ]

4)In [ショートカット]→「リンク先」 Append the following command

  「 -J-Dfile.encoding=MS932」

  the whole 「リンク先」 looks like:

        “C:\Program Files\IFS\DeveloperStudio22.12\bin\developer_studio64.exe”  -J-Dfile.encoding=MS932

5)Use that Shortcut to boot IFS Dev Studio.

Reply