User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0

Steps to reproduce:

I am running Firefox 79.0 on Fedora Silverblue 32, via the org.mozilla.firefox Flatpak on Flathub.

When I middle-click scroll ("auto scroll"), Firefox crashes extraordinarily frequently. It doesn't happen all the time, but it happens often enough that it's crashing over and over and over and over again throughout my day, always while I'm middle-click scrolling. If I avoid middle-click scrolling, it no longer crashes.

Steps to reproduce:

1. Enable "Use autoscrolling" in the browser preferences.
2. Load a web page.
3. Click the middle-mouse button to enter middle-click scrolling mode.
4. Move the mouse to scroll around.

Actual results:

Firefox often crashes (but not always).

When it crashes, I get the following GUI message:
"Mozilla Crash Reporter
Firefox had a problem and crashed. We'll try to restore your tabs and windows when it restarts.
Unfortunately the crash reporter is unable to submit a crash report.
Details: The application did not leave a crash dump file."

If I run Firefox from the terminal via the command "flatpak run org.mozilla.firefox", then I get the following terminal output:
"ExceptionHandler::GenerateDump cloned child 1286
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error."

Expected results:

Firefox should scroll smoothly without crashing. Firefox should be stable.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

No crash report makes this harder to diagnose. Maybe you can attach gdb or lldb and trigger a crash?

For what it's worth FF 79-82 exhibited this behaviour for me, using a vanilla distribution package without Flatpak (Arch Linux, Gnome/Wayland, Webrender, AMD graphics), but this seems to be fixed in Firefox 83.0.

I can confirm I'm no longer experiencing this issue with Firefox 83.0. Looks like it has been fixed!