Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1692565 - Select all text crashes firefox wayland [NEEDINFO]
Summary: Select all text crashes firefox wayland
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 29
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ffwayland
TreeView+ depends on / blocked
 
Reported: 2019-03-25 21:42 UTC by Adam Chasen
Modified: 2019-03-26 11:45 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
stransky: needinfo? (adam)


Attachments (Terms of Use)

Description Adam Chasen 2019-03-25 21:42:06 UTC
Description of problem:
Either "ctrl+a" or right click and "select all" in a text box (Gmail and Zendesk) will cause browser to segfault: https://retrace.fedoraproject.org/faf/reports/2502326/

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


How reproducible:
Consistently reproducible on boot once behaviour experienced.

Restart will remedy the situation for an undetermined amount of time.


Steps to Reproduce:
1. open firefox-wayland
1. open email editor (gmail)
2. type text
3. press ctl-a

Actual results:
segfault

Expected results:
select all text

Additional info:
attempted to include backtrace, but original was too big to be accepted (1.4G larger than 1.2G limit) and backtrace locally was "not enough information to be useful" as reported by the tool

Comment 1 Adam Chasen 2019-03-25 21:46:55 UTC
correction, I am not consistently able to reproduce. I restarted firefox wayland and I do not experience this bug.

Comment 2 Martin Stransky 2019-03-26 11:45:28 UTC
Can you try to update to 66.0.1 and submit the crash via ABRT when it happens again? Thanks.


Note You need to log in before you can comment on or make changes to this bug.