Conversation

Notices

1. Embed this notice
   Yohan Yukiya Seseㆍ사요한・謝雪矢 (youronlyone@c.im)'s status on Sunday, 06-Aug-2023 09:05:48 JST Yohan Yukiya Seseㆍ사요한・謝雪矢

   Something is wrong with #Mozilla #Firefox 116 b8 under #PopOS 22.04.

   It keeps hanging, or crashing, when there are #JavaScript interactions.

   What I've tried:
   * Uninstall Firefox
   * Delete all profiles
   * Delete all cache
   * Reboot
   * Install Firefox
   * Test from a fresh installation, Without any customizations and addons/extensions.
   * Disabled HTTP3 (which was the issue for a similar case a year ago).
   * No, I don't have popcorntime installed (which is/was an issue for #Wayland.)
   * I'm using #X11 not Wayland.

   Other information:
   * I can't even login to #Google. After entering my password, the tab just stops working. It stops interacting. No clicks, no tabbing, no arrow cursor.
   * I can't event open `about:support` it hangs.
   * I can't use #Facebook, eventually the tab will stop interacting. No clicks, no tabbing, no arrow cursor.
   * I can't watch videos on #YouTube. If the YT ads play first, it will get stuck there. If the actual video plays first, after a few seconds it will either get stuck at some frame, or just keep playing without any interaction (can't stop, etc.)

   My device:
   * Pop!_OS 22.04 which is #Ubuntu / #Debian based.

   This is totally out of my league. I don't know what else to test.

   So, I switched to #Naver #Whale as my primary #browser for now. It is a #Chromium-based browser from #Korea.

   Oh, one more thing, when I close Firefox, it pops-up an error that it crashed. Since the 116b8 update, Firefox just kept on crashing when closing.

   #Linux #bugs #bug #support #YourOnlyOne #techmagus

   @youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml

   • Embed this notice
     Yohan Yukiya Seseㆍ사요한・謝雪矢 (youronlyone@c.im)'s status on Sunday, 06-Aug-2023 09:27:37 JST Yohan Yukiya Seseㆍ사요한・謝雪矢

     in reply to

     • Matt :opensuse: :wayland:

     @thelinuxcast

     Good question! Forgot that.

     Just tested it with `--safe-mode` flag and everything works fine.

     Without the flag… found the culprit. See attached file.

     @youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml

   • Embed this notice
     Matt :opensuse: :wayland: (thelinuxcast@fosstodon.org)'s status on Sunday, 06-Aug-2023 09:27:38 JST Matt :opensuse: :wayland:

     in reply to

     @youronlyone@c.im @youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml Have you tried to run it from the terminal to see what errors pop out?

   • Embed this notice
     Yohan Yukiya Seseㆍ사요한・謝雪矢 (youronlyone@c.im)'s status on Sunday, 06-Aug-2023 10:13:50 JST Yohan Yukiya Seseㆍ사요한・謝雪矢

     in reply to

     • Matt :opensuse: :wayland:

     @thelinuxcast

     I disabled hardware acceleration, and the hang-up / crash took longer.

     Then I enabled #Wayland in Pop_OS 22.04 (disabled by default) and switched to it, and now #Firefox 116 b8 is working fine, but with hardware acceleration (without it, it's lagging).

     I guess time to switch to Wayland. ^_^;;

     @youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml

   • Embed this notice
     Matt :opensuse: :wayland: (thelinuxcast@fosstodon.org)'s status on Sunday, 06-Aug-2023 10:13:51 JST Matt :opensuse: :wayland:

     in reply to

     @youronlyone@c.im @youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml hmm. Usually when mesa errors are happening it's a driver issue, but I've never seen it effect just one app before.

     You could try Firefox-ESR.

   • Embed this notice
     Yohan Yukiya Seseㆍ사요한・謝雪矢 (youronlyone@c.im)'s status on Sunday, 06-Aug-2023 10:15:39 JST Yohan Yukiya Seseㆍ사요한・謝雪矢

     in reply to

     • Matt :opensuse: :wayland:
     • SweetAI Belle :sweetunsure:

     @SweetAIBelle

     Tried that, and the hang-up / crash took longer before it happened.

     I guess there's a libEGL / X11 / FF combination that is no longer working fine with 116 b8.

     When I enabled Wayland in Pop_OS 22.04 and switched to it, FF 116 b8 started to work smoothly. Though with hardware acceleration enabled under Wayland.

     @thelinuxcast @youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml

   • Embed this notice
     SweetAI Belle :sweetunsure: (sweetaibelle@equestria.social)'s status on Sunday, 06-Aug-2023 10:15:40 JST SweetAI Belle :sweetunsure:

     in reply to

     • Matt :opensuse: :wayland:

     @youronlyone@c.im @thelinuxcast @youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml

     How about if you go into settings, uncheck "Use recommended performance settings" and then uncheck "Use hardware acceleration when available"?

   • Embed this notice
     Yohan Yukiya Seseㆍ사요한・謝雪矢 (youronlyone@c.im)'s status on Sunday, 06-Aug-2023 13:37:45 JST Yohan Yukiya Seseㆍ사요한・謝雪矢

     in reply to

     @youronlyone@firefish.social Update #2:

     It wasn't exactly fixed. Just that, there are some sites that are now affected, and the initial sites I tested are now fine.

     It's like switching to Wayland only changed which sites are hanging-up / crashing.

     This time I can't open any of Amazon's websites, I can't use Google search (just for testing), and other sites.

     @Linux@chirp.social @linux@lemmy.ml

   • Embed this notice
     Yohan Yukiya Seseㆍ사요한・謝雪矢 (youronlyone@c.im)'s status on Sunday, 06-Aug-2023 13:48:47 JST Yohan Yukiya Seseㆍ사요한・謝雪矢

     in reply to

     • Matt :opensuse: :wayland:
     • SweetAI Belle :sweetunsure:

     @SweetAIBelle Yeah. I thought it was too.

     I wonder what changed. I regularly clear logs, I had cleared my update logs before I noticed something's wrong.

     I'm going to give Firefox from Flathub a try later. Maybe there's some system dependency that's conflicting.

     @thelinuxcast @youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml

   • Embed this notice
     SweetAI Belle :sweetunsure: (sweetaibelle@equestria.social)'s status on Sunday, 06-Aug-2023 13:48:49 JST SweetAI Belle :sweetunsure:

     in reply to

     • Matt :opensuse: :wayland:

     @youronlyone@c.im @thelinuxcast @youronlyone@firefish.social @Linux@chirp.social @linux@lemmy.ml
     Ah, all right. Figured it was worth a try, in case the hardware acceleration was the issue...

   • Embed this notice
     Yohan Yukiya Seseㆍ사요한・謝雪矢 (youronlyone@c.im)'s status on Monday, 07-Aug-2023 16:51:57 JST Yohan Yukiya Seseㆍ사요한・謝雪矢

     in reply to

     • Matt :opensuse: :wayland:
     • deltatux :donor:

     @deltatux

     For testing new stuff on the webdev side. Also, to know what's next and not get surprised just when it's critical. Like now, I noticed these things when it wasn't a critical day.

     @Linux @thelinuxcast @youronlyone@firefish.social

   • Embed this notice
     deltatux :donor: (deltatux@infosec.town)'s status on Monday, 07-Aug-2023 16:51:59 JST deltatux :donor:

     in reply to

     • Matt :opensuse: :wayland:

     @youronlyone@c.im @thelinuxcast@fosstodon.org @youronlyone@firefish.social @Linux@chirp.social
     
     Consider running the stable branch instead of the beta branch? Is there a reason you're using Firefox Beta?
     
     Also consider installing via Flatpak, could resolve some dependency issues as well.