Bug 1676331

Summary:	[Wayland] crashes not listed in coredumpctl or abrt-cli list, only Mozilla reporter
Product:	[Fedora] Fedora	Reporter:	Chris Murphy <bugzilla>
Component:	firefox	Assignee:	Martin Stransky <stransky>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	29	CC:	0xalen+redhat, anto.trande, bugzilla, gecko-bugs-nobody, jgrulich, jhorak, john.j5live, kengert, pjasicek, rhughes, rstrode, sandmann, stransky
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-28 11:50:12 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 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):
firefox-65.0-4.fc29.x86_64


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


Steps to Reproduce:
1. Crash firefox
2.
3.

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 https://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products ? 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
> https://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products ?

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 4 Chris Murphy 2019-02-19 20:09:16 UTC

https://crash-stats.mozilla.com/report/index/e321bb3a-0865-4aff-8923-086a90190219#tab-details

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 - https://koji.fedoraproject.org/koji/taskinfo?taskID=33102407