Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1693911

Summary: [regression] [wayland] freeze, then crash, while searching in address bar
Product: [Fedora] Fedora Reporter: Dimitris <dimitris>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 29CC: 0xalen+redhat, anto.trande, fedora, gecko-bugs-nobody, jhorak, john.j5live, kengert, pjasicek, rhughes, rstrode, sandmann, stransky
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-23 13:31:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1054334    

Description Dimitris 2019-03-29 02:14:10 UTC
Description of problem:

Twice in the same day following upgrade to v66 (currently at 66.0.1-1.fc29)

Version-Release number of selected component (if applicable):

66.0.1-1.fc29

How reproducible:

Sporadic

Steps to Reproduce:
1. Start private window
2. Start typing in the address bar
3. Initial character gets registered multiple times (reported previously at https://bugzilla.redhat.com/show_bug.cgi?id=1693091)
4. Firefox freezes for a few seconds, then SIGSEGVs.
5. abrt says "uReport data is invalid"

Actual results:

Freeze then crash

Expected results:

Previous to v66 I haven't had a Firefox crash in months, if not years.

Additional info:

There is a coredump under /var/spool/abrt but I'm not sure how to extract a useful stack trace.

Comment 1 Martin Stransky 2019-07-23 13:31:33 UTC

*** This bug has been marked as a duplicate of bug 1693091 ***