# BrowserEngine Crashed **URL:** \ **Category:** Ignition\ **Tags:** vision\ **Created:** [January 2, 2024, 8:46pm UTC](https://forum.inductiveautomation.com/t/browserengine-crashed/83715 "2024-01-02T20:46:40Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![jtdfan](https://avatars.discourse-cdn.com/v4/letter/j/a88e4f/32.png) [@jtdfan](https://forum.inductiveautomation.com/u/jtdfan)\ **Post date:** [January 2, 2024, 8:46pm UTC](https://forum.inductiveautomation.com/t/browserengine-crashed/83715/1 "2024-01-02T20:46:40Z")
I have a customer whose Vision Client Launcher (8.1.32) is failing to launch any client due to the following error. Details is greyed out. We have cleared cache. Uninstalled / Reinstalled. Still the same issue. Any ideas would be appreciated. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/b/fbf93cc12ce35f73af3d4a18d5b20817203ee22f.png) ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 2, 2024, 9:44pm UTC](https://forum.inductiveautomation.com/t/browserengine-crashed/83715/2 "2024-01-02T21:44:46Z")
You can get more information (usually) if you look at your vision client launcher's log file, extract the java command at the end that it uses to launch the real client, and run that manually in a terminal. Then you will likely see everything that is going wrong. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [January 2, 2024, 10:10pm UTC](https://forum.inductiveautomation.com/t/browserengine-crashed/83715/3 "2024-01-02T22:10:40Z")
Is it actually _failing to launch_ (there sure appears to be a client in the background of your screenshot), or is this error just appearing and then the client starts the rest of the way up? JxBrowser failing to launch is not fatal to the client launch as of some recent version, though it's possible it _appears_ to be failing if you're embedding a web browser component on one of your initial startup window(s). ---
**Author:** ![jtdfan](https://avatars.discourse-cdn.com/v4/letter/j/a88e4f/32.png) [@jtdfan](https://forum.inductiveautomation.com/u/jtdfan)\ **Post date:** [January 3, 2024, 7:47pm UTC](https://forum.inductiveautomation.com/t/browserengine-crashed/83715/4 "2024-01-03T19:47:07Z")
So the app does run, but there is no window that starts up with the WebBrowser module. There is a window that can be clicked on that has the WebBrowser embedded. This doesn't happen on other client machines. Would there be a particular reason why it wouldn't work on one machine vs another? ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [January 3, 2024, 7:54pm UTC](https://forum.inductiveautomation.com/t/browserengine-crashed/83715/5 "2024-01-03T19:54:14Z")
There might be a more useful error message in that particular client's diagnostics console (Ctrl + Shift + F7). From experience, it's usually some failure to extract temporary files caused by antivirus/OS file permissions/cosmic rays/whatever. I forgot about the details of the ticket I alluded to - if you're using the web browser module at all, we do attempt to initialize it as soon as the client launches, for faster startup once you actually navigate to a window that uses the component. That process happens in the background and is normally silent, _unless_ something goes wrong. ---
**Author:** ![mweber1](https://avatars.discourse-cdn.com/v4/letter/m/e79b87/32.png) [@mweber1](https://forum.inductiveautomation.com/u/mweber1)\ **Post date:** [October 7, 2024, 6:27pm UTC](https://forum.inductiveautomation.com/t/browserengine-crashed/83715/6 "2024-10-07T18:27:40Z")
In my client logs, I have a ERROR designer.JXBrowserUtil -- Could not initialize browser Engine, platform is not supported. The client here is running on Win2012R2 (soon to be upgraded), but is this the issue? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [October 7, 2024, 6:30pm UTC](https://forum.inductiveautomation.com/t/browserengine-crashed/83715/7 "2024-10-07T18:30:07Z")
> [@mweber1](#): > > The client here is running on Win2012R2 (soon to be upgraded), but is this the issue? Yes, Google dropped support for Windows 2012 in Chrome/Chromium. ---
**Author:** ![rodimus.prime](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/rodimus.prime/32/77608_2.png) [@rodimus.prime](https://forum.inductiveautomation.com/u/rodimus.prime)\ **Post date:** [July 10, 2025, 10:45pm UTC](https://forum.inductiveautomation.com/t/browserengine-crashed/83715/8 "2025-07-10T22:45:00Z")
I have the same error, but I am also using Citrix. The app is actually opening for me. I just get the error and I would like to stop it from showing. It only has Vision Client Launcher installed and when I looked at the visionclientlauncher.log, I didn't see any errors. But I did see that this in the log 4 times. > JVM-wide ObjectInputFilter set up successfully > Platform serialFilter has 88 pattern(s) > Set initial logging level to INFO > Attempting to connect to gateway http://gateway\_ip:80 > Starting Java with the following parameters I did try extracting the java commands and I running that in a terminal. The result was that the project opened and I got the error message. I went to the log afterward but I didn't see any errors in there. Do you have any other suggestions that I can try to stop the error message from showing? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [July 10, 2025, 11:05pm UTC](https://forum.inductiveautomation.com/t/browserengine-crashed/83715/9 "2025-07-10T23:05:08Z")
Are you running on an OS that Chrome doesn't support any more? Other than working with support to possibly fix the underlying problem, assuming it's something else besides an unsupported OS, I think the only other thing that can be done is to stop using the Web Browser module. ---
**Author:** ![rodimus.prime](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/rodimus.prime/32/77608_2.png) [@rodimus.prime](https://forum.inductiveautomation.com/u/rodimus.prime)\ **Post date:** [July 11, 2025, 2:20pm UTC](https://forum.inductiveautomation.com/t/browserengine-crashed/83715/10 "2025-07-11T14:20:05Z")
No, I'm not. We are using Chrome Version 109.0.5414.168 on Windows Server 2012 R2. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 11, 2025, 2:29pm UTC](https://forum.inductiveautomation.com/t/browserengine-crashed/83715/11 "2025-07-11T14:29:37Z")
> [@rodimus.prime](#): > > We are using Chrome Version 109.0.5414.168 No, Ignition uses its own chromium, downloaded from the target gateway to match the JxBrowser version used. If you are trying to run modern Ignition on an old OS, you won't get around this. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [July 11, 2025, 2:41pm UTC](https://forum.inductiveautomation.com/t/browserengine-crashed/83715/12 "2025-07-11T14:41:12Z")
> [@rodimus.prime](#): > > on Windows Server 2012 R2. You'll have to uninstall the web browser module entirely to get rid of that error message.