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
Bug 1676331 - [Wayland] crashes not listed in coredumpctl or abrt-cli list, only Mozilla reporter
Summary: [Wayland] crashes not listed in coredumpctl or abrt-cli list, only Mozilla re...
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 29
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ffwayland
TreeView+ depends on / blocked
Reported: 2019-02-12 02:16 UTC by Chris Murphy
Modified: 2019-02-28 12:01 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-02-28 11:50:12 UTC
Type: Bug

Attachments (Terms of Use)

Description Chris Murphy 2019-02-12 02:16:17 UTC
Description of problem:

I've got a 100% crash reproducer if I paste in about 100 lines and then place cursor either at the top or bottom, then shift click to highlight a large (50+line) portion. This is new in FF65. But when this crashes, there's no coredumpctl listing, or abrt-cli list listing. The crash is only reported by the Firefox/Mozilla crash reporter, and I have no feedback from that reporter where it's filing the bug upstream.

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

How reproducible:
At least for this crash, always. I haven't had any other crashers yet.

Steps to Reproduce:
1. Crash firefox

Actual results:

No coredumpctl or abrt-cli listing, no upstream bug listing.

Expected results:

I expect to get a bug ID so I can track the bug, make sure I've supplied enough information so it can get fixed. But the existing behavior permits no reporting that can be tracked.

Additional info:

Comment 1 Chris Murphy 2019-02-12 23:00:19 UTC
For what it's worth, this crash is 100% reproducing only with "Firefox on Wayland" if I launch the "Firefox" application, I never get this crash. But again I can't really report any details because, no crash logs locally, just the mozilla crash reporter comes up.

Comment 2 Martin Stransky 2019-02-19 10:14:32 UTC
Can you please create and attach a backtrace according to ? The Abrt is not very useful for us anyway as we generally need more precise ones. Thanks!

Comment 3 Chris Murphy 2019-02-19 19:38:34 UTC
(In reply to Martin Stransky from comment #2)
> Can you please create and attach a backtrace according to
> ?

After reproducing the crash and typing 'thread apply all bt full' the system becomes unresponsive for 30 minutes, fans running at maximum. This is a laptop with 8GB RAM, and 4GB swap, and gdb uses all the RAM and 1/2 the swap. The crash_bt file remains 0 bytes for the entire duration. So I killed it. This isn't a helpful way to debug firefox problems. If there's something wrong with abrt and/or the retrace server, it needs to be fixed. If I knew in advance this was going to take an hour of gdb processing and not melt my laptop in the process, I might consider it but there's no progress so after 1/2 an hour I killed it.

Comment 5 Martin Stransky 2019-02-28 11:50:12 UTC
Thanks. I enabled the ABRT for Fedora 30 to catch Wayland and other crashes on Fedora 30. The package is not ready yet, it's in firefox-65.0.

Comment 6 Martin Stransky 2019-02-28 12:01:16 UTC
Actually I enabled it for Fedora 29. Builds are there -

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