Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox 68 closing immediately when an application tries open a web interface , NO Error shown

  • 2 replies
  • 1 has this problem
  • 3 views
  • Last reply by cor-el

more options

My application opens a web interface using the default browser supported both in Windows and Red Hat .Before firefox 68 all was fine , but from the latest release of firefox , problem started in windows , the browser closes immediately with out displaying anything . In Linux all is fine . Also in IE the result is OK .

There is no error coming when the browser closes. Anything changed in the latest version in the firefox which might be causing this .

Thanks for your help

My application opens a web interface using the default browser supported both in Windows and Red Hat .Before firefox 68 all was fine , but from the latest release of firefox , problem started in windows , the browser closes immediately with out displaying anything . In Linux all is fine . Also in IE the result is OK . There is no error coming when the browser closes. Anything changed in the latest version in the firefox which might be causing this . Thanks for your help

Chosen solution

Hi ghosh.rituparna, could you describe this in a little more detail: how does your application start Firefox?

Firefox 68 uses a new launch(er) process on Windows. You can read more about that in the following wiki page:

https://wiki.mozilla.org/Platform/Integration/InjectEject/Launcher_Process/

Read this answer in context 👍 1

All Replies (2)

more options

Chosen Solution

Hi ghosh.rituparna, could you describe this in a little more detail: how does your application start Firefox?

Firefox 68 uses a new launch(er) process on Windows. You can read more about that in the following wiki page:

https://wiki.mozilla.org/Platform/Integration/InjectEject/Launcher_Process/

more options

Maybe try the process monitor utility to see if that gives some clues about where this goes wrong.

See also: