Web Browser Module "Crash" on Vision Client startup (Linux)

I just upgraded Ignition Edge from 8.1.24 to 8.1.31. Everything went as expected until I went to launch the Vision Client. When the project starts, I receive the following error message:
"BrowserEngine crashed. Exceeded crash count, will not reload. crash count: 3"

I suspected this was the Web Browser module. Upon checking the Gateway, I see that the Browser module is Active and Loaded, but not running. I can't seem to find anyplace on the Gateway page to indicate an error however.

I removed and re-installed the Vision Client on the client machine (Linux) but the error persists (redownloaded the launcher, extracted, and loaded the project via the Launcher). I downloaded the Client to Windows machine and there is no issue.

Is this an issue with the Linux client?

Edge Gateway v8.1.31
Web Browser Module v5.1.31
Vision Module v11.1.31

Client launchers were the 8.1.31 versions (64bit tar for Linux and Exe for Windows)


Any additional error information is going to be on the machine running the Vision Client.

Check ~/.ignition/clientlauncher-data for a log file and upload it here if you can. Inside that log file there's going to be a long message where it logs the command it actually used to launch a client. Copying that command into a terminal and running it there will allow you to get the actual log output from launching a client.

1 Like

I removed the log, then relaunched. Here is the newly created log:
visionclientlauncher.log (1023 Bytes)

I didn't see any errors here.
I also ran this command in terminal but I did not see any output related to the error.

Can you share a screenshot or copy/paste the entire error you're seeing?

Sorry for the bad photo, can't get a screenshot.

"BrowserEngine crashed. Exceeded crash count, will not reload. crash count: 3"

Hmm. I would have expected that to show up in the terminal output when you launch manually using the command.

Does this Vision project use the browser component on any screens?

Which command? This, exactly as it appears in the logs?

nohup /home/operator/.ignition/cache/resources/runtimes/11.0.18/bin/java -classpath /home/operator/.ignition/cache/resources/platform/launchclient.jar/000000002C867024/launchclient.jar -Djavaws.sr.gateway.addr.0=https://localhost:8043 -Djavaws.sr.launchts=1694538072405 -Djavaws.sr.main=com.inductiveautomation.factorypmi.application.runtime.ClientLaunchHook -Djavaws.sr.platform.edition=edge -Djavaws.sr.platform.plugins=edge-panel,edge-iiot -Xms32M -Xmx256M -Djavaws.sr.memory.init=32M -Djavaws.sr.memory.max=256M -Dsun.java2d.d3d=false -Dsun.java2d.noddraw=false -Djavaws.sr.screen=0 -Djavaws.sr.scope=C -Djavaws.sr.project=Edge com.inductiveautomation.ignition.client.launch.BootstrapSwingFS & 

Try dropping the nohup and the trailing &, so that the process is still attached to the current terminal:

/home/operator/.ignition/cache/resources/runtimes/11.0.18/bin/java -classpath /home/operator/.ignition/cache/resources/platform/launchclient.jar/000000002C867024/launchclient.jar -Djavaws.sr.gateway.addr.0=https://localhost:8043 -Djavaws.sr.launchts=1694538072405 -Djavaws.sr.main=com.inductiveautomation.factorypmi.application.runtime.ClientLaunchHook -Djavaws.sr.platform.edition=edge -Djavaws.sr.platform.plugins=edge-panel,edge-iiot -Xms32M -Xmx256M -Djavaws.sr.memory.init=32M -Djavaws.sr.memory.max=256M -Dsun.java2d.d3d=false -Dsun.java2d.noddraw=false -Djavaws.sr.screen=0 -Djavaws.sr.scope=C -Djavaws.sr.project=Edge com.inductiveautomation.ignition.client.launch.BootstrapSwingFS
1 Like

No, it doesn't but I had added the module thinking I may need it at some point.


That did it! Redirected the output to the attached file.
output.txt (45.1 KB)

What distro and version of Linux is this?

Looks like some dependencies may need to be installed for JXBrowser to work.

Debian 9.13 (Stretch)
It sounds as if there were updates to the Client launcher between 8.1.24 and 8.1.31 that would require some updated dependencies?

The client launcher isn't really relevant here. By design, it doesn't know know much of anything about the gateway(s) it's connected to. The error you're getting is happening after the launcher's responsibility is over; it's launched the process to run the actual client - it's just that the client now can't run because of a dependency or other issue with JxBrowser.

If you're not actually using it, the easiest thing to do would be to just uninstall the module.

1 Like

I've removed it for now.
If the issue is on the Gateway, is there any reason I would only get this error when launching the client locally vs. running a remote client from my Windows machine?

It’s not a problem on the gateway, the local client machine running this is where the error occurs.

1 Like

Missing libraries, for future reference:

14:15:21.282 WARNING Failed to find libudev.so.0x.x.x
14:15:21.283 [Chromium Process Thread] WARN com.teamdev.jxbrowser - Failed to find libudev.so.0x.x.x
14:15:21.284 WARNING Failed to find libgcrypt.so.1x.x.x
14:15:21.285 [Chromium Process Thread] WARN com.teamdev.jxbrowser - Failed to find libgcrypt.so.1x.x.x
14:15:21.286 WARNING Failed to find libcrypto.so.1x.x.x
14:15:21.287 [Chromium Process Thread] WARN com.teamdev.jxbrowser - Failed to find libcrypto.so.1x.x.x

You would need to figure out which packages provide these libraries and install them. Debian -- Package Search Results -- libcrypto

Stretch is old, though... you can't even filter for it.

I think of the latter two, you only need one. I get this in my designer console on startup:

09:13:13.370 [Designer-Startup] INFO Perspective.Designer - Starting up Perspective module.  Mode: Trial
9:13:13.567 WARNING Failed to find libgcrypt.so.1x.x.x
09:13:13.571 [Chromium Process Thread] WARN com.teamdev.jxbrowser - Failed to find libgcrypt.so.1x.x.x

and the designer runs fine. I think because my system has libcrypto.so.1.1 provided by libssl.

(My system has libgcrypt20 installed, but JxBrowser doesn't seem to use it.)

FWIW, JxBrowser claims support for Ubuntu 20.04, which is partly why I'm still using Kubuntu 20.04 as my daily driver.

Thanks. I was hunting for these late yesterday and gave up. I know Stretch is old, but the embedded PC I am using came from MOXA pre-imaged with other utilities (ThingsPro) I had planned to use, and unfortunately they do not supply it on a later release. So I am a bit constrained with how much I can do to this box.

If I end up needing the web browser module I can revisit.