Found 6 results for crash for Firefox for Enterprise

Firefox ER version 68.11 - 32 bit crashing on launch

Hi Everyone, We are in the middle of deploying Firefox ESR 68.11 (32-bit) on Windows 10 1903. The deployment is sucessfull so the application is installed correctly. but when we launch from desktop of menu shortcut, it crashes every time with: Sorry, we're having trouble having your page back. (see image attach). Re-installing does not change anything... I tried deleting the User profile registry entries and the %Localappdata%\Mozilla folder without any success. the message in the Event viewer is: Log Name: Application Source: Application Hang Date: 21/08/2020 11:14:34 AM Event ID: 1002 Task Category: (101) Level: Error Keywords: Classic User: N/A Computer: Description: The program firefox.exe version 68.11.0.7506 stopped interacting with Windows and was closed.

Choosing a Firefox CPU architecture for Windows OS

Desktop compatibility Firefox 32 bit Firefox 64 bit 32 bit OS Supported Not supported 64 bit OS Supported Supported Systems with more than 2 GB RAM Supported Supported Systems with 2 GB RAM or less Supported Supported but not recommended(lower performance) Benefits and limitations of 64 bit Firefox Firefox 32 bit Firefox 64 bit Lower crash rates No Yes (we observed a crash rate reductionin the order of 50% to 60% after migratingrelease channel users to 64 bit Firefox) Higher security (ASLR) No Yes 32 bit only extensions Yes No (vendors may have 64 bit compatibleextensions though) Citrix XenApp users willing to use 64 bit Firefox, see 64-bit Firefox crashes with Citrix's XenApp VM.

Choosing a Firefox update channel

Rapid release: receives major updates every four weeks and minor updates such as crash fixes and security fixes as needed during those four weeks. Extended Support Release (ESR): receives major updates on average every 42 weeks with minor updates such as crash fixes, security fixes and policy updates as needed, but at least every four weeks. In addition to different update cycles, the ESR currently has access to additional policies that are not available on rapid release.

Silent Auto Update for Firefox ESR

Here is settings in an old .cfg file that I am testing with: lockPref("app.update.mode", 1); lockPref("app.update.service.enabled", true); lockPref("extensions.update.enabled", false); lockPref("extensions.update.autoUpdateEnabled", false); // Set default homepage - users can change // Requires a complex preference defaultPref("browser.startup.homepage","data:text/plain,browser.startup.homepage=http://workday"); // Don't ask to install the Flash plugin lockPref("plugins.notifyMissingFlash", false); // Disable Search Engine automatic updates lockPref("browser.search.update", false); //Disable telemetry lockPref("toolkit.telemetry.prompted", 2); lockPref("toolkit.telemetry.rejected", true); lockPref("toolkit.telemetry.enabled", false); // Disable health reporter lockPref("datareporting.healthreport.service.enabled", false); lockPref("datareporting.healthreport.logging.consoleEnabled", false); lockPref("datareporting.healthreport.uploadEnabled", false); // Disable all data upload (Telemetry and FHR) lockPref("datareporting.policy.dataSubmissionEnabled", false); // Disable crash reporter lockPref("toolkit.crashreporter.enabled", false); Components.classes["@mozilla.org/toolkit/crash-reporter;1"].getService(Components.interfaces.nsICrashReporter).submitReports = false; // Don't show WhatsNew on first run after every update pref("browser.startup.homepage_override.mstone","ignore"); // Don't show 'know your rights' on first run pref("browser.rights.3.shown", true);

Firefox ESR version stops loading periodically

background.js:2 x4 moz-extension://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/background/background.js:2 However, this appears to be happening just this morning, and I have not experienced the freezing issue in this time frame. So after talking to the development team, it seems like the content process is crashing for some reason. Do you see anything in about:crashes on these machines? This might be something better discussed in bugzilla as a bug versus here.

Kiosk Usage

But often their DLL would be buggy, or it would make bad assumptions about how Firefox works, or the way Firefox works would change in a way that they didn't expect, and ultimately Firefox would crash because of it. Most people don't know about all this, so they just assume that it is Firefox's fault that it's crashing and get mad at us instead of at their antivirus. We can sort of do some things that prevent this from happening, but even if we do it really early in startup, people might inject their code even earlier than that.