Does this happen when you load a specific channel or randomly? Also, go to the View menu and select Developer Tools for Current Server and see if there are any error messages.
Just happened here again, seems to be random.
see the log file. It shows network disconnects which were not apparent to me,
not sure if this is related but it happens frequently on WiFi, LAN,
and also other laptops in other networks.
https://pastebin.com/xA0uNzz9
Also on another machine
https://pastebin.com/a7vdDFs3
Hi, @nanocosmos-ol
Besides the ERR_NAME_NOT_RESOLVED and ERR_TIMED_OUT that I can see from the log, I noticed the following as well:
websocket_client.jsx:49 websocket re-established connection
websocket_actions.jsx:481 channel broken because of too many incoming messages
websocket_actions.jsx:481 channel broken because of too many incoming messages
Since the app complains that the channel is broken due to the incoming messages, can you share a little more on the following:
- Mattermost Server version
- Mac OS version
- Mattermost Mac OS app version (if you are not on the latest version, can you upgrade to the latest 4.4.0?)
- The number of open channels / DM on the RHS channel list
Server Version: 5.19.0 (integrated with gitlab)
Build Number: 5.19.1
MacOS: different versions, 10.13, 10.14, 10.15
MacApp version 4.4 (latest), running from source / electron same issue
Open channels: about 30 with about 20 users
(what is RHS channel list?)
Is it possible to book professional support to work together on this?
Can you send me a direct message?
Same problem popped up for me on a new machine.
GPU accel already disabled.
Old machine was Manjaro (latest, mattermost-desktop 4.4.0, no problem)
New machine, same setup but XFCE instead of KDE desktop
I cant even make use of the webkit debugger console as that one is completely unresponsive as well, stops rendering anything, turns black and crashes mattermost after a minute.
Whenever mm-dektop receives a messages it’s unresponsive for about a minute, barely usable in this state.
Freeze only happens if client has no focus on receiving a message. And apparently only with XFCE desktop. So probably something is going haywire with the notification framework used/involved
Temporary solution for everyone experiencing this problem:
/usr/bin/chromium --profile-directory=Default --app=https://your.mattermost.server…
Put it in Autostart and be happy.
Also Notifications are finally working as intended with this solution as it uses the chromium Framework for that
Hi, everyone.
Update on this. @nanocosmos-ol shared this to me:
but at the same time, would like to know if @Xnyle 's solution can also help. Maybe you might want to give it a try.
Wrong guess - I just updated to Ubuntu 20.04 and Mattermost Desktop 4.5.4 and the same issue still persist.
It only seems to happen if a notification sound is played. As already written, the UI stays aktive, even the cursor continues blinking, but it does not react to any user interaction for a long time, after which it resumes normal operation.
It’s definitely a bug in the application somewhere.