Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Browser crashing on some webpages

  • 14 antwurd
  • 0 hawwe dit probleem
  • 1 werjefte
  • Lêste antwurd fan marcoshalano

more options

I'm using Firefox 106.0.1 on Ubuntu 22.10 from Mozilla's official PPA but when I open some websites the browser crashes with the message "Exiting due to channel error.". I found the error could be related to libwebp with LTO enabled, may be it is, but I rebuilt the Ubuntu's package without LTO and one website stopped crashing, dell.com support page, but several others still crash, like amd.com.

I'm using Firefox 106.0.1 on Ubuntu 22.10 from Mozilla's official PPA but when I open some websites the browser crashes with the message "Exiting due to channel error.". I found the error could be related to libwebp with LTO enabled, may be it is, but I rebuilt the Ubuntu's package without LTO and one website stopped crashing, dell.com support page, but several others still crash, like amd.com.

Keazen oplossing

I found the problem. It was related to speech as crash reports showed. The problem was I had the package libspeechd2 installed in my machine, since my main machine passed for some updates and wasn't a clean install. I just removed the package and worked.

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (14)

more options

Try downloading Firefox from Mozilla, unzip, and run firefox-bin from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release

The AMD site works for me. see screenshot Do you have the same issue with your distro version of Firefox in Safe Mode?

Bewurke troch jonzn4SUSE op

more options

Hi @jonzn4SUSE, I still get the crash, even using the binary directly. I think is some ABI incompatible with Ubuntu 22.10, because it works with Firefox Snap version that, I think, doesn't share libraries and stuff.

☸ minikube (default) in ~/Downloads/firefox on ☁️ (us-east-2) took 11s ➜ ./firefox-bin Gtk-Message: 20:47:04.105: Failed to load module "xapp-gtk3-module" [GFX1-]: glxtest: VA-API test failed: failed to initialise VAAPI connection. [2022-10-22T23:47:06Z ERROR glean_core::metrics::ping] Invalid reason code startup for ping background-update ExceptionHandler::GenerateDump cloned child 1383862 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Gtk-Message: 20:47:09.931: Failed to load module "xapp-gtk3-module" 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.

more options

What desktop? X11 or Wayland?

more options

GNOME desktop with X11. The strange is: there is no problem in a clean installation I did in a VM (using the build from Mozilla). Can be multiple factors, like graphics card (I use NVIDIA) or something old (since that's not a new installation). Do you know how can I produce debug info about the execution? The logs aren't very informative.

more options

We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.

The crash report is several pages of data. We need the report numbers to see the whole report.

  1. Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted/Unsubmitted Crash Reports will appear, similar to the one shown below.
  2. Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.

Note: If a recent Report ID does not start with bp- click on it to submit the report.

(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)

Fx64Beta-aboutcrashes-unsubmitted

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

more options

Hi Paul, here is the IDs: bp-5073f2d4-8828-4da1-8625-32ea00221023 bp-abd9ea9d-10d4-4f82-9d2c-f293a0221020 bp-67d84b39-3639-4fcb-b7ee-d90170221013 bp-ec3fca81-802b-44a2-b26a-7dd110220711 bp-cc0f98c6-0add-46c5-8f1c-6c0d30220303

I made question to crash on purpose (opening amd.com) multiple times. I think if you can debug this you can debug any other crash.

more options

The crashes still happens on safe mode, but the log error is slightly different

more options

I found this bug. The bug was related to Ryzen 1st gen, but I think it could affect Intel processors in a different way (the syscall isn't the same). https://bugzilla.mozilla.org/show_bug.cgi?id=1794057

more options

marcoshalano said

Do you know how can I produce debug info about the execution? The logs aren't very informative.

The screenshot is tracing an already running process of Firefox. see screenshot You should run this if you want to trace from the beginning.

strace -o firefox_log -t firefox &

The output (the -o option) will be huge, but you will have to narrow it down to the time (the -t option) of the issue.


Operating System: openSUSE Tumbleweed 20221026 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.3-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU E3-1535M v5 @ 2.90GHz Memory: 62.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: HP Product Name: HP ZBook 17 G3

Bewurke troch jonzn4SUSE op

more options

This is just a shoot in the dark, but found this. https://askubuntu.com/questions/1396739/failed-to-load-module-xapp-gtk3-module

more options

Related to your link about xapp-gtk3-module, that's not the problem. It occurs a lot with other applications. I think it could be related to my NVIDIA GPU or sandbox. Here is the link to the trace. I was able to get everything since the browser just popped up and I wen to amd.com, where the crash always happens. https://www.dropbox.com/s/d6wuvvad8u51g1o/firefox_log.zip?dl=0

more options

Just to confirm... The issue only happens in the snap version and not in Firefox from Mozilla? If so, you should hit the snap forum and provide the log file.

more options

It's the exactly opposite. The problem doesn't occur on Snap version, just on non-confined versions, can be the tar.bz2 I download from the website or the package I download from Mozilla PPA.

more options

Keazen oplossing

I found the problem. It was related to speech as crash reports showed. The problem was I had the package libspeechd2 installed in my machine, since my main machine passed for some updates and wasn't a clean install. I just removed the package and worked.