Status

()

Firefox
Untriaged
--
critical
RESOLVED WORKSFORME
a year ago
a year ago

People

(Reporter: victorkrynytsky, Unassigned)

Tracking

52 Branch
x86_64
Windows 8.1
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

a year ago
Created attachment 8844616 [details]
Firefox 52 crash.jpg

Hello! After updating to version 52 of the version of Firefox it was completely impossible to use it. See attached screenshot.

Updated

a year ago
Group: firefox-core-security

Comment 1

a year ago
Are there errors in the browser console, if you can open that up? Does it open in safe mode (use the --safe-mode commandline option)? Can you open it with a clean profile? ( https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles )
Component: General → Untriaged
Flags: needinfo?(victorkrynytsky)
(Reporter)

Comment 2

a year ago
I can not now clear Firefox, about 50 tabs are open and they need to be processed first. But the error only appeared when updating to 52 versions. Previously, there were no mistakes when working with Firefox.
(Reporter)

Comment 3

a year ago
Also I downloaded the crashfirefox.exe file, run this file and sent a report about the fall of Firefox.

Comment 4

a year ago
(In reply to victorkrynytsky from comment #3)
> Also I downloaded the crashfirefox.exe file, run this file and sent a report
> about the fall of Firefox.

Can you post a link (from about:crashes)? We get millions of crashreports, so just saying you sent one won't help me find it...

Using a new profile doesn't require you to remove or alter your existing profile, and it might get you back a working browser.

While I understand that it might seem 'obvious' that the problem was with 52, if 51 worked correctly, there were thousands of changes between 51 and 52. Without more details about the circumstances in which 52 doesn't work (like add-ons, particular preferences, maybe particular websites, etc.), it will be impossible for us to fix anything based on this report.
(Reporter)

Comment 5

a year ago
Message ID bp-bd20f0fd-66eb-4e1f-a44a-7fb902170307

Yes, you are right, before installing the 52 version, Firefox worked fine all the years.

Comment 6

a year ago
It appears from the screenshot and stack that Firefox is having trouble painting the window, but isn't actually "hung". Could you clarify the exact behavior you're seeing?

Clarifying whether you can still reproduce this even in safe mode with a new profile would help narrow this down, as would getting your about:support data. Getting that from the "broken" profile would be best, but if you can't getting it from the safe-mode profile would still be helpful.
(Reporter)

Comment 7

a year ago
The problem was resolved a few minutes ago. I downloaded the version of Firefox 52 and installed it over the installed one. Firefoh works now normally. Thank you for your help!

Comment 8

a year ago
ok. I wish we knew why, but I don't think it makes sense to try and go back to figure it out.
Status: UNCONFIRMED → RESOLVED
Last Resolved: a year ago
Flags: needinfo?(victorkrynytsky)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.