The first thing to do would be to try and collect some logs by following the instructions in this post: [FB12678-Investigating] Issues with upgrade
It is not necessary to attempt the ‘lightweight’ mode test mentioned a couple posts after that on (so don’t bother with the -Dperspective.browser.mode.lightweight=true flags, those are only applicable on osx). Trying the ‘memory based cache’ might be useful, but you’ll want to make sure you give the designer 2 GB of ram minimum (set the memroy using the JRE flag -Xmx2048m through the jvm flags described in the designer launcher docs, or by setting the ‘max memory’ value.
Forward us the logs that result.
After doing that, you may want to attempt using an alternate JDK. Azul is excellent, and JDK’s are generally 99.9999% identical (I made up that number, point being there should not be any detectable difference), but small differences may exist on some operating systems depending on how they are compiled. Oracle Certified alternatives with commercially friendly licenses include Amazon Corretto and AdoptOpenJDK. I don’t expect a different result, but if one of those did work, it would give us some valuable information to bring to the Azul team. Technically you only need the ‘JRE’ (java runtime environment), but the JDK (Java Development Kit, which includes a JRE) provides some additional tools that may be helpful in troubleshooting
To configure a custom JDK/JRE for use when launching the designer, you’ll need to:
- locate the
designer-launcher.jsonfile. This is generally found in{USER_HOME_DIR}/.ignition/clientlauncher-data/designer-launcher.json - Set the json’s following properties to true and the alternate java executables path:
"use.custom.jre": true,
"custom.jre.path": "{ALTERNATIVE_JAVA_HOME}/bin/java"
- Save the file
- restart the computer to make sure any errant processes are not hanging in the background or potentially binding ports
- attempt launching the designer launcher/designer again after the reboot
Send us any logs you can come up with, and let us know if you see any changes if you try the alt JDK.