Open evren320 opened 2 years ago
I have noticed similar behaviour on Windows. It started happening after updating to v6.1.0. It renders WhatsApp to be completely unusable. Everything freezes, it's impossible to write messages and certain actions on keyboard such as backspace to remove characters in message composer don't work at all.
also seeing this on 6.0.0-nightly.39 on mac os 12.5.1 (21G83) for a week or so now
also seeing this on 6.0.0-nightly.39 on mac os 12.5.1 (21G83) for a week or so now
You are too far behind on Ferdium versioning.... You should start to have multiple problems with that version.
Please, manually update to the most recent stable or nightly/beta.
Still a lot of lagging problems with whatsapp using ferdium 6.1.1.nightly.8-1.
I've updated to 6.1.0. I noticed that things seemed nicely responsive after leaving it for a while, but as soon as I put in a message with a non-alphanumeric (it was ?
) it went back to being laggy.
I don't know if it is the same issue, but with the 6.1.0 release, I had to delete and rebuild my entire Ferdium profile folder. Prior to rebuild it, WhatsApp, on my machine (openSUSE Linux) was unusable: any time I tried to add an emoticon, or I tried to move with cursos keys or cut and paste text, the application become unresponsive, and often the WhatsApp tab crashed. After rebuild the folder profile (~/.config/Ferdium on Linux) all this issues are disappeared.
I can confirm the bug on 6.1.0 and that deleting ~/.config/Ferdium
"solves" the problem.
Another observation, not sure if it's related: Before and after removing the folder, WhatsApp's built-in "update" doesn't work. When I click "Update WhatsApp", something happens and the update notification is gone, but then, when I reload the page, the update notification appears again.
Same problem as here on Windows: https://github.com/ferdium/ferdium-app/issues/581 .
I am using WhatsApp both on windows and mac and they both run horribly. I honestly don't even know if it is a Ferdium issue, since WhatsApp is just garbage.
I'm having a similar issue to this. Every time I recieve a whatsapp message ferdium freezes and I get the error (ferdium:133237): libnotify-WARNING **: 15:24:38.606: Failed to connect to proxy
If I disable whatsapp the rest of ferdium works perfectly so it's definitely a whatsapp error
I have stopped using Whatsapp in Ferdi months or even a year ago for this type of problem; I haven't yet tried to use it in Ferdium.
FWIW, the experience was more or less smooth in my regular browser (Waterfox) but even there I'm now seeing lags when moving the cursor 1 character at a time.
I think it's Whatsapp doing something "clever" in their text entry field...
Avoid duplicates
Ferdium Version
6.1.0 Also tried 6.0.0-nightly.7 same behavior
What Operating System are you using?
Other Linux
Operating System Version
Manjaro Kernel 5.15.60-1
What arch are you using?
x64
Last Known Working Ferdium version
No response
Expected Behavior
Doing certain actions in whatsapp, for example writing something, pressing left or right arrow to fix a typo, or pressing home or end to go begin or end of the textbox, it should be fast and normally do its function.
Actual Behavior
Doing those actions makes ferdium to freeze and spike high cpu and ram usage on task manager, ultimately freeze it forever randomly, but it just remains frozen, does not crash, unusable. It sometimes randomly happen when clicking other chat rooms, clicking emoji or attachment button too.
Steps to reproduce
Sometimes but randomly, clicking another chat room, clicking emoji button, or attachment, or trying to view a photo on chat history also causes spikes.
Debug link
https://debug.ferdium.org/c6661dac-81f1-4f6a-93ee-7d11b5ed7039
Screenshots
Additional information
Using Whatsapp web on a browser, i did not encounter this bug. Using Windows version of Ferdium, i did not encounter this bug I have tried to clear cache, it didn't change the result. I have tried to remove/reinstall ferdium, ferdium-nightly, and result didn't change. Disabling hardware acceleration on ferdium doesn't change the result. Disabling KDE Compositor doesn't change the result.
I have attached a screenshot of 60 seconds developer tool profiling page and reproduce the bug 5 times in that timespan.