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

64 bit edition of Firefox does not respond when using configuration files

  • 4 replies
  • 2 have this problem
  • 27 views
  • Last reply by a.m.l.

more options

Hi there,

Firefox 64-bit does not respond when starting with configuration files like override.ini, autoconfig.js, mozilla.cfg, etc. It does not depend on which files or which settings. Firefox even didn't work if only using override.ini (containing: [XRE] EnableProfileMigrator=false). This may only be a problem when creating a new Firefox profile for a users. Since i use a nonpresistent VDI (Citrix), i did not test other scenarios.

No problems with 32-bit Firefox.

here is my setup: - Firefox 53.0 (64-bit) German - Windows Server 2012 R2 (64-bit) German - autoconfig.js (placed in %InstallDirFirefox%\browser\defaults\preferences or %InstallDirFirefox%\defaults\pref) - override.ini (placed in %InstallDirFirefox%\browser) - UserChrome.css (placed in %InstallDirFirefox%\browser\defaults\profile\chrome) - mozilla.cfg (placed in %InstallDirFirefox%)

Chosen solution

The configuration files of Firefox were not the cause for the bug, but the Multi-Process-spawning (Electrolysis) of Firefox when running on Citrix XenApp 7.13 XenApp hooks some API calls of Firefox. This causes the bug. Citrix XenApp will disabled the hooks for Firefox 64bit executables in some feature version (reference fixed issue ID LC6982).

Read this answer in context 👍 0

All Replies (4)

more options

Already created a bug report, as this is pretty easy to reproduce:

https://bugzilla.mozilla.org/show_bug.cgi?id=1359443

more options

Did you use Firefox 64 to create these files or did you create the files outside Firefox?

more options

Those files are created manually as described in

https://developer.mozilla.org/en-US/Firefox/Enterprise_deployment

more options

Chosen Solution

The configuration files of Firefox were not the cause for the bug, but the Multi-Process-spawning (Electrolysis) of Firefox when running on Citrix XenApp 7.13 XenApp hooks some API calls of Firefox. This causes the bug. Citrix XenApp will disabled the hooks for Firefox 64bit executables in some feature version (reference fixed issue ID LC6982).