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:
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.
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!
(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.
https://crash-stats.mozilla.com/report/index/e321bb3a-0865-4aff-8923-086a90190219#tab-details
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.
Actually I enabled it for Fedora 29. Builds are there - https://koji.fedoraproject.org/koji/taskinfo?taskID=33102407