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
correction, I am not consistently able to reproduce. I restarted firefox wayland and I do not experience this bug.
Can you try to update to 66.0.1 and submit the crash via ABRT when it happens again? Thanks.
(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?
(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.
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.
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
Please reopen if you can reproduce with latest nightly.