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 - [regression] [wayland] freeze, then crash, while searching in address bar
Summary: [regression] [wayland] freeze, then crash, while searching in address bar
Keywords:
Status: CLOSED DUPLICATE of bug 1693091
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ffwayland
TreeView+ depends on / blocked
 
Reported: 2019-03-29 02:14 UTC by Dimitris
Modified: 2019-07-23 13:31 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-23 13:31:33 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.