Closed Bug 1626991 Opened 6 years ago Closed 6 years ago

Firefox Quantum 74 Crashes Suddenly When Clicking on Input Fields

Categories

(Core :: Widget: Gtk, defect)

74 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1624745

People

(Reporter: bbigby64, Unassigned)

Details

(Keywords: crash)

Attachments

(2 files)

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.162 Safari/537.36

Steps to reproduce:

I was logging into the page,

https://zoom.us/signin

and when I clicked on an input field, the browser crashed. I've seen this with other sites, too.

Actual results:

All of my browser windows disappeared immediately so Firefox crashed.

Expected results:

I should have enable to enter my data/login credentials and proceed without the browser crashing.

This application has not been configured to display crash reports.

Please open about:preferences#privacy-reports and check if crash reporting is enabled. If it isn't, please enable it and restart Firefox.
Then try to reproduce the crash, open about:crashes and copy the crash ID(s) (bp-xxxxx) over to Bugzilla. Thanks!

Keywords: crash

I attached a png of what selected in about:preferences, and all of the relevant properties appear to be on, but after exiting the browser, restarting it, and inducing the crash, when I access the about:crashes page, the page displays a message which states that there were no crashes.

All of the reporting options appear to be active, but after a crash, I enter about:crashes and I see no crash reports.

Update 4/7/2020

To reproduce it, I do the following:

  1. Go to https://bugzilla.mozilla.org

  2. Click 'Log in'

  3. Enter your credentials, and click Login

  4. Then, I click on your avatar in the upper right corner of the window, and a drop down menu appears.

  5. Click 'Preferences'.

  6. Click in the field, 'New password:'.

  7. Type a few random characters.

  8. Now, attempt to Backspace beyond the beginning of the input field; Firefox crashes -- at least for me, it does.

I can reproduce a crash every time with these steps.

By the way, I updated my Firefox to 74.0.1 on Fedora 3.1 with recent updates.

Sorry, I meant, Fedora 31.

Hi,
I tried reproducing this issue in ubuntu 18.0 using the following versions

Firefox Nightly 77.0a1 (2020-04-07) (64-bit)
Beta 76.0b1 (64-bit)
Release 75.0 (64-bit)

But also firefox 74.0 as mentioned in your report.

We do not have right environment set up in order to reproduce this issue but I will set the component for it and maybe one of our developers will be able to reproduce it on their end using Fedora.

Thanks for the report.

Best regards,

Clara.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

I have another desktop (Intel i7 Haswell 4c/8t, 32 GB 1600 Mhz RAM) running Fedora 31 with Firefox 74.0.1 as well, and I just tried to reproduce the problem with the steps that I described previously, and the browser wouldn't crash. I'll try the same test on my other machine but under a different account. I wonder whether the problem is specific to the account on my other desktop (AMD Ryzen 9 3950X, 16c/32t, 64 GB 3200 MhzRAM).

Update

I logged into a different Linux account on my Fedora 31 desktop computer, and I could not reproduce the crash using the steps that I outlined previously. Then, I returned to my regular account and reproduced the crash. I decided to rename my $HOME/.mozilla directory to $HOME/.mozilla.bak, and restart Firefox 74.0.1. This forced Firefox to reinitialize the part of its state that lives under .mozilla. After doing this, I could NOT reproduce the crash. Apparently, something within my .mozilla subdirectory tree was in a bad state. Could it be data that was not saved to the disk in an atomic way, which left some data in a bad state? Regardless, I can't reproduce the crash anymore, or at least not with the steps that I documented previously. Consequently, I will resume using Firefox again.

I think this is a dupe of Bug 1624745 which was backported to 74.0.1.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: