dr460nf1r3/firedragon-browser

Whatsapp.web crashes after minutes and complains about storage space

Opened this issue Β· 21 comments

I'm trying to use web.whatsapp.com beta in FireDragon. Problem is, no matter what I do, the website crashes 5 to 10 minutes after first opening it. The error message below is shown, then when I click ok I get logged out of the website and retrying login leads to the same result.

image
(Translation: "There's not enough storage space in your system for WhatsApp to work. Delete some unused files to free up space in your computer then try logging in again." - I couldn't get this cursed website to show up in english no matter what I did, I guess it looks up your IP address and not your system locale. Talk about annoying.)

What I've tried so far, to no avail:

  • Permitting everything WhatsApp could possibly ask for
  • Turning off fingerprinting block in security options
  • Turning off Enhanced Tracking Protection
  • Turning off DuckDuckGo Privacy Essentials
  • Turning off Dark Reader
  • Turning on vanilla Firefox sync
  • Turning on DRM
  • Changing general.useragent.override to mimick the latest Firefox release

Strangest of all is that the problem is nowhere to be seen in LibreWolf or vanilla Firefox. So it must be something related to FireDragon's modifications. I really didn't want to change browsers, as I'm liking this so far.

Any ideas? Thanks!

I get straight up this, no option to use the beta:
image

Hey :) first of all I'd suggest this, but I'm suspecting its rather one of the additional patches rather than the configs. I'll provide a test build without them soon since I don't have a Whatsapp account to do testing with.

I already deleted these config files, actually for the issue you just linked.

So I neither think, its that.
Otherwise great work!

Update v98 has been released, there were some changes to build flags, they are now closer to Librewolf. Could you try if that improves things?

Seems like v98 didn't change anything on this issue. I'll try deleting the firedragon.cfg later today.

I get straight up this, no option to use the beta

Btw, @ShalokShalom, you can solve this by changing the general.useragent.override property to something like Mozilla/5.0 (X11; Linux x86_64; rv:97.0) Gecko/20100101 Firefox/97.0, in the about:config page. This will make websites think you're using the latest official Firefox browser.

Hey :) first of all I'd suggest this, but I'm suspecting its rather one of the additional patches rather than the configs. I'll provide a test build without them soon since I don't have a Whatsapp account to do testing with.

Just tested this here. Moved /usr/lib/firedragon/firedragon.cfg to somewhere else completly. Nothing changed, website still crashes after 5~10 minutes. I'm having to use it in LibreWolf for the time being πŸ˜”

This is a build without Gentoo patches, which LibreWolf itself doesn't add. Please try and report back :)

This is a build without Gentoo patches, which LibreWolf itself doesn't add. Please try and report back :)

Finally tried this, sorry for the delay. After unistalling current version and installing this one with sudo pacman -U, firedragon simply doesn't open anymore. When I tried to launch it from the console, it spat out this:

XPCOMGlueLoad error for file /usr/lib/firedragon/libxul.so:
libicui18n.so.70: cannot open shared object file: No such file or directory
Couldn't load XPCOM.

All goes back to normal if I reinstall the latest Firedragon. But web.whatsapp.com still glitches the same way.

One other thing I tried these days was manually allowing persistent data for the website, in the permissions tab of the ctrl + i menu. But it had no effect.

My whatsapp works now.

My whatsapp works now.

For real? It still bugs the same way here. I'm running 99.0.1.

One thing I found out is that I can sorta bypass the error by pressing Esc. Seemed to work like a miracle for some ~20 minutes, but then the error came back again. I kept dismissing it but it started reappearing faster and faster each time, until it appeared almost instantaneously after I dismissed the last error :(

Edit: oops, accidentally closed the issue…

To be sure: You deleted or moved the default config, yes?

#25 (comment)

To be sure: You deleted or moved the default config, yes?

#25 (comment)

I did. Still, the same bug happens. Really strange stuff.

Here's something that might help, the terminal output when I open FireDragon and then try using web.whatsapp a bit. The error occurred twice in this test run.

To be sure: You deleted or moved the default config, yes?
#25 (comment)

I did. Still, the same bug happens. Really strange stuff.

Here's something that might help, the terminal output when I open FireDragon and then try using web.whatsapp a bit. The error occurred twice in this test run.

Did you try with a new profile? There is a even a plugin, that helps you switching between these. https://addons.mozilla.org/en-US/firefox/addon/profile-switcher/

Did you try with a new profile? There is a even a plugin, that helps you switching between these. https://addons.mozilla.org/en-US/firefox/addon/profile-switcher/

Tried this and the issue seemed to magically disappear for like an hour. But then it came back the same way as before. Tried ignoring the error message but it kept reappearing faster each time, until the site became unusable.

For now I'm making do with WALC.

Edit: Just tried disabling ALL my extensions for testing. No effect whatsoever, still crashes after 15~20 minutes.

The latest build got really close to Librewolf configuration wise. I thought this would be a good thing as Librewolf is quite stable. Could you try and report back whether this is still an issue on the latest build?

Just tried it, still an issue πŸ˜”

Edit: and it seems now the tab keeps crashing completly, which didn't happen before:

image

Nothing changed, website still crashes after 5~10 minutes. I'm having to use it in LibreWolf for the time being pensive

Did you try Librewolf? Can you reproduce there?

If this can still be reproduced; please hit F12 to open Developer Tools, then go to the console, click gear in top right, check persist logs, and then see if there are any useful or relevant errors logged before or during the tab crashes.

Tab isn't crashing completly these days, but unfortunately the initial problem still happens, rendering the website unusable. Works perfectly in LibreWolf and vanilla Firefox.

Here's the logs in the console when the error occurs.

@vinivosh:

Use of drawWindow method from CanvasRenderingContext2D is deprecated. Use tabs.captureTab extensions API instead https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/tabs/captureTab pagedata-script.js:1:12465

Were you trying to take a screenshot or something at the end of this?

Can you set privacy.partition.serviceWorkers to false in about:config?

wagrod commented

@vinivosh:

Use of drawWindow method from CanvasRenderingContext2D is deprecated. Use tabs.captureTab extensions API instead https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/tabs/captureTab pagedata-script.js:1:12465

Were you trying to take a screenshot or something at the end of this?

Can you set privacy.partition.serviceWorkers to false in about:config?

Hey. I also have the same problem as the colleague reported.
I set privacy.partition.serviceWorkers to false, but it didn't work.
I use garuda linux.