Window freezes after message received

[TheRolf]

It is possible to send/receive messages for a while, then the whole window (excluding the menu bar) freezes, and it is not possible to click on anything. Pressing F5 also does not help.

[lefterisgar]

Which version are you using and on what OS?

[rivenirvana]

Experiencing this as well since upgrading to upstream 2.56. Fresh install and configs, on both appimage and COPR packages.

[lefterisgar]

It's very weird because we have tested Caprine on all major OSs and this issue didn't show up.

[lefterisgar]

Does it freeze after resizing?

[TheRolf]

Sorry: Windows 10 Enterprise, and I updated to the latest (2.56.0), and that is doing it. Except the "Relaunch" and "Work chat" options, nothing in the menu does anythinghas any effect when clicked. When resizing: the inside stays the same, and the window just "crops" it when resizing, nothing else happens.

[lefterisgar]

Sounds like an Electron issue. Does everything work fine if you don't resize the window?

[TheRolf]

I start Caprine, then I do not alter the size, yet this happens. Or do you mean keeping the original size after installation?

[lefterisgar]

I meant the first. Resizing it after starting the app.

[lefterisgar]

Really weird though.

@dusansimic Any idea?

[TheRolf]

It also does not seem to need a trigger, if I keep the window idle, it happens; as well as sometimes during typing.

[lefterisgar]

I'm not really sure but something has probably happened at Facebook's end (a UI change) that has broken most of the features. It can't be explained otherwise. Even my dev setup has issues including a black rectangular box on top of the UI.

[lefterisgar]

On my machine the following don't work:

• Most dark theme icons
• Hide names and avatars
• Show message buttons
• Show Active Contacts
• Show Message Requests
• Show Hidden Threads
• All conversation related options

[rivenirvana]

Can confirm those features are not working. Also:

• Blocking indicators settings missing/broken
• File -> Messenger Settings (ctrl+comma) not working

[lefterisgar]

Yeah, and much more probably. It's not related to the new release though. Tested with the previous one too. It's Meta to blame!

At this point just wait for a new release.

[TheRolf]

Can confirm all of these. Weird minor thing: after freezing, the GIFs are still playing :) @lefterisgar so they broke things the same time the new release came out?

[lefterisgar]

@lefterisgar so they broke things the same time the new release came out?

I'm wondering about the same. Does the old one work for you? It doesn't for me. Also, I was daily driving a "beta" version of what came to be this release and didn't have those issues. After all, it might be a coincidence!

[TheRolf]

Yes, same behaviour with 2.55.6!

[lefterisgar]

What a coincidence! Besides that, expect a release, probably tomorrow if all goes well.

[rosoau]

On Ubuntu 22 at first no access to menus, (*after resize) then a freeze, then cannot access the 5th or so Friend and then freeze again then window opens to: oops something went wrong and now Logout not working but all the rest is OK again these issues were not present on 2.55.7-1

[godspede]

Confirming that the same thing started happening to me today on Windows. I was on a version of 2.55 and decided to update, but that didn't change anything. Dev console is spitting up a "Minified React error #418" error, and a bunch of warnings about source maps not being valid JSON (although I wouldn't be surprised if those are related to something else). There's also a weird black bar between the main content of the app and the menu bar (screenshot below)

The usual location.reload() trick isn't working out, unfortunately. Must be a change/problem on Messenger's side.

[lefterisgar]

On Ubuntu 22 at first no access to menus, (*after resize) then a freeze, then cannot access the 5th or so Friend and then freeze again then window opens to: oops something went wrong and now Logout not working but all the rest is OK again these issues were not present on 2.55.7-1

I can only say about the resizing issue which is well known (#1871) and is caused by a newer Electron version, not by us. 2.55.7-1 used Electron 13 and we have since updated to 20!

The rest, as @godspede says are caused by Messenger and it happened that they rolled out a new design the day after we pushed a release!

[godspede]

The rest, as @godspede says are caused by Messenger and it happened that they rolled out a new design the day after we pushed a release!

[lefterisgar]

• Blocking indicators settings missing/broken

All broken features were intentionally disabled in this release to avoid confusion and bug reports until they are fixed.

[TheKrakenator]

Same here, freezes by itself and has to be terminated through task manager. 2.55.5 and Windows 10.

[leventelist]

I experience the same, but the CPU load goes to 100% on a single core. On Debian Linux.

[marko19914]

Fedora 36, Caprine 2.55.7, flatpak version. Freezes if message is recieved when the app window is out of focus. No freeze when message is recieved in focus.

[lefterisgar]

I experience the same, but the CPU load goes to 100% on a single core. On Debian Linux.

This is really weird. No such issue on (K)Ubuntu 22.04. Keep in mind, however, that Caprine is essentially a whole Chromium instance (browser) running in the background. There might be a problem in the underlying framework we use (Electron) but that's up to them to fix.

[dusansimic]

Sorry for a late reply. I haven't experienced these kinds of issues (I use Arch, Fedora and test dev version by just running npm start).

Could it be something Electron related? Some older issues on Electron repo suggest that it might be related to the Linux kernel but it seems to happen on Windows too.

[54ac]

Same here, 2.56.0 on Windows 10. Hangs and becomes completely unresponsive every time a message is received and has to be restarted. Very annoying.

[marko19914]

Fedora 36, Caprine 2.55.7, flatpak version. Freezes if message is recieved when the app window is out of focus. No freeze when message is recieved in focus.

There was an update to the flatpak (to 2.56.0). Seems to be fixed in that version.

[damnsonitswilly]

Kept hanging on mine (Windows 11, v2.56.0) so back to FB's official messenger app until it's fixed. Hoping for an update soon, their layout is so bland compared to Caprine 😂

[kacnje]

I can confirm freezing on two of my computers after installing 2.56.0. Computer1 uses Windows 10, computer2 uses Linux Mint 21.

[lefterisgar]

@damnsonitswilly, @kacnje is it any better with v2.56.1?

[rtm516]

I have the same issue with 2.56.0 and 2.56.1, for me it works fine until I receive a message in the currently opened chat then it freezes.

[kacnje]

No, it still freezes with 2.56.1. Just tested.

[rosoau]

I can confirm like wise. It also freezes on Xubuntu 22.04 with gnome flashback session and version 2.56.1 Every few minutes it has to be terminated and restarted. Just long enough to organise a phone call as an alternative :-)

[marko19914]

Fedora 36, Caprine 2.55.7, flatpak version. Freezes if message is recieved when the app window is out of focus. No freeze when message is recieved in focus.

There was an update to the flatpak (to 2.56.0). Seems to be fixed in that version.

Should say, that after updating it is now weird for me. It at some point it freezes. Cannot really understand when.

[Comandeer]

I also have the issue, v. 2.56.1 on Linux Mint 20.3. I noticed that the freeze appears when a new message arrives.

[tbeckerson]

I'm having the same problem - Caprine becomes unresponsive when a new message arrives. I can use the File>Relaunch Caprine option to restart, but the problem happens again whenever another message comes in. It freezes even when I'm in a different conversation.

Version 2.56.1 on Arch Linux.

[dusansimic]

Now I have experienced this issue but not on every received message, just some of them. I'm still not sure what caused it soo we'll investigate it.

[54ac]

It happens in random intervals for me. Hangs on every message received for a few hours, then works fine again for a few hours, etc.

[dusansimic]

I've locked this thread because not much useful information is being posted. If someone has something that could help, send us an email (mine is on my profile page). We'll post here if anything new is discovered.

[dusansimic]

It seems that all package formats are affected, so it's expected that everyone is experiencing the issue. If anyone has anything other than that to report, reach out to developers.