Bug 1692565

Summary:	Select all text crashes firefox wayland
Product:	[Fedora] Fedora	Reporter:	Adam Chasen <adam>
Component:	firefox	Assignee:	Martin Stransky <stransky>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	29	CC:	0xalen+redhat, anto.trande, fedora, gecko-bugs-nobody, jhorak, john.j5live, kengert, pjasicek, rhughes, rstrode, sandmann, stransky
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
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:26:52 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 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.

Comment 3 Christian Stadelmann 2019-05-14 20:38:42 UTC

(In reply to Martin Stransky from comment #2)
> Can you try to update to 66.0.1 and submit the crash via ABRT when it
> happens again? Thanks.

I think I ran into this or a similar bug quite often lately, but I am unable to report it because gdb consumes all of my 16GB of memory during analyzing the backtrace and then gets OOM-killed. Is there anything you can do about that?

Comment 4 Martin Stransky 2019-05-15 09:28:52 UTC

(In reply to Christian Stadelmann from comment #3)
> (In reply to Martin Stransky from comment #2)
> > Can you try to update to 66.0.1 and submit the crash via ABRT when it
> > happens again? Thanks.
> 
> I think I ran into this or a similar bug quite often lately, but I am unable
> to report it because gdb consumes all of my 16GB of memory during analyzing
> the backtrace and then gets OOM-killed. Is there anything you can do about
> that?

Please try Firefox nightly. Fedora packages are built with PGO which doesn't work well with gdb.

Comment 5 Adam Chasen 2019-05-15 13:43:40 UTC

Can you point to a recommended wayland nightly build? I recently upgraded to F30 and haven't experienced this yet. It may take a few weeks for it to appear though. I was not able to reliably reproduce the conditions to cause this bug.

Comment 6 Martin Stransky 2019-05-15 13:58:50 UTC

I suspect this is something that depends on Gtk+ version and it may be already fixed. 
Info how to test mozilla binaries is here - https://fedoraproject.org/wiki/How_to_debug_Firefox_problems?rd=Bug_info_Firefox#Testing_Mozilla_binaries

Comment 7 Martin Stransky 2019-07-23 13:26:52 UTC

Please reopen if you can reproduce with latest nightly.