Rocket.Chat icon indicating copy to clipboard operation
Rocket.Chat copied to clipboard

5.2.0 Has erratic jittering behaviour as new messages appear

Open thrakks opened this issue 2 years ago • 22 comments

Description:

After updating to 5.2.0 the chat will jitter and bounce around as it erratic refreshes whilst new messages appear. (See attached GIFs for examples)

Steps to reproduce:

  1. Have a similar setup to me?
  2. Update to 5.2.0
  3. Post messages in a chat channel or direct to a person

Expected behavior:

Messages appear without the erratic jittering bouncing around behavior

rc5 2 0-expected

Actual behavior:

Chat bounces and jitters erratic whilst is refreshes a new message appearing:

rc5 2 0-actual

Server Setup Information:

  • Version of Rocket.Chat Server: 5.2.0
  • Operating System: Centos 7.9/Docker
  • Deployment Method: RC: Docker / Mongo: Centos7.9 passthrough
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: Whatever version is included in the official rocketchat docker image
  • MongoDB Version: 5.0.6

Client Setup Information

  • Desktop App or Browser Version: MacOS Chrome 106.0.5249.119
  • Operating System: macOS Monterey 12.6

Additional context

I was able to immediately rollback to my previous server version of 5.1.2 and the problem went away again. As soon as I then re-upgrade to 5.2.0 the problem is immediately present.

Relevant logs:

Not sure there's anything relevant to show. GIFs show best what is occuring.

thrakks avatar Oct 21 '22 04:10 thrakks

I've noticed that since 5.2.0 some chats are opened at the middle of chat history and continue loading and jittering at the same time. Don't know if it's possible to provide any debug info on this issue...

IKrendelev avatar Oct 21 '22 07:10 IKrendelev

Ok I was able to reproduce this using the admin user in both 5.2 and 5.3-rc2. However...

I tried another user, and it didn't happened. Even created a new one, set avatar, and tried all sorts of things.

For the user with the jittering, looks like it renders the message as a unique, then renders it again to fit into the group of messages from the same user (I had to record it and play it in slow motion to conclude that).

Thanks for pointing it out!

dudanogueira avatar Oct 21 '22 13:10 dudanogueira

I'm glad it's a reproducible bug and not some strange occurrence only on my hodge podge setup.

thrakks avatar Oct 23 '22 23:10 thrakks

Ok I was able to reproduce this using the admin user in both 5.2 and 5.3-rc2. However...

I tried another user, and it didn't happened. Even created a new one, set avatar, and tried all sorts of things.

For the user with the jittering, looks like it renders the message as a unique, then renders it again to fit into the group of messages from the same user (I had to record it and play it in slow motion to conclude that).

Thanks for pointing it out!

Guess it's all about new and legacy parser. New parser looks much better here, old parser have that jittering.

@dudanogueira can you test that?

ankar84 avatar Oct 24 '22 03:10 ankar84

Ok I was able to reproduce this using the admin user in both 5.2 and 5.3-rc2. However... I tried another user, and it didn't happened. Even created a new one, set avatar, and tried all sorts of things. For the user with the jittering, looks like it renders the message as a unique, then renders it again to fit into the group of messages from the same user (I had to record it and play it in slow motion to conclude that). Thanks for pointing it out!

Guess it's all about new and legacy parser. New parser looks much better here, old parser have that jittering.

@dudanogueira can you test that?

I require legacy parser due to my company's deep seeded reliance in rendering Tables in certain team channels. That rendering feature is still bugged in the new parser :(

image

thrakks avatar Oct 24 '22 03:10 thrakks

Guess it's all about new and legacy parser. New parser looks much better here, old parser have that jittering. @dudanogueira can you test that?

I require legacy parser due to my company's deep seeded reliance in rendering Tables in certain team channels. That rendering feature is still bugged in the new parser :(

image

Actually I stuck with old parser as you because of https://github.com/RocketChat/Rocket.Chat/issues/27065

ankar84 avatar Oct 24 '22 05:10 ankar84

this problem has a bad effect on the users experience, is there no temporary solution???

majidh1 avatar Oct 29 '22 08:10 majidh1

Same thing but:

  • changing or disabling markdown parser has no effect
  • message history completely reloads after new message or hitting reply button ul.messages-list keeps refreshing. Downgrading to 5.1.4 resolves this isse. 5.2 and 5.3 has described behaviour.

terR0Q avatar Nov 01 '22 20:11 terR0Q

@terR0Q thanks We had to downgrading version 😔

majidh1 avatar Nov 02 '22 07:11 majidh1

@dudanogueira Hey, Duda! Looks like it is one of the most critical problem of recent 5.2.0 and 5.3.0 Can you highlight it to Front-End team?

ankar84 avatar Nov 02 '22 08:11 ankar84

Just upgraded to 5.3 and we are seeing the same behavior, it seems to be related to the legacy parser.

skeleton55 avatar Nov 03 '22 09:11 skeleton55

Just upgraded to 5.3 and we are seeing the same behavior, it seems to be related to the legacy parser.

I too upgraded to to 5.3 but thought it was gone. (Entirely forgetting I had disabled the legacy parser and I'm an idiot)

Re-enabled legacy parser and I too can confirm problem still exists in 5.3

thrakks avatar Nov 03 '22 23:11 thrakks

How can legacy parser be disabled?

terR0Q avatar Nov 05 '22 21:11 terR0Q

How can legacy parser be disabled?

Administration -> Settings -> Accounts-> Default User Preferences -> Use legacy message template (Disable the toggle)

Then hard refresh/reload cache your browser/chat app. The Awful super jitter refresh should go away, but you'll lose the ability to used markdown Tables and other such cool features.

thrakks avatar Nov 06 '22 22:11 thrakks

Other than loosing useful markdown features this way seems pretty inconvinient as has to be performed under every user in a system. I'll leave it be with 5.1.4 for a couple of months with way you described as last resort. Thank you anyway!

terR0Q avatar Nov 07 '22 23:11 terR0Q

Other than loosing useful markdown features this way seems pretty inconvinient as has to be performed under every user in a system. I'll leave it be with 5.1.4 for a couple of months with way you described as last resort. Thank you anyway!

By change the default user preference via Administration, it applies to all users. At least it did for my 30 or so users. They just had to hard refresh/invalidate cache their browser/chat app and it works.

thrakks avatar Nov 07 '22 23:11 thrakks

Still not fixed in 5.3.2 ?

krenuser avatar Nov 20 '22 19:11 krenuser

Still not fixed in 5.3.1. The changelog for 5.3.2 does not show anything that looks like it would solve the problem.

We're still using the old parser due to #26492/#26388 which is closed despite still being broken.

ebyrne242 avatar Nov 21 '22 20:11 ebyrne242

Still not fixed in 5.4.0. What is even the point. Someone from the Rocketchat team please address that this is still a known bug. :(

thrakks avatar Dec 06 '22 04:12 thrakks

If i may ask to give this bug some priority - we are loosing user acceptance every day and this started with Version 5.2.0. So a lot of Days in between. Yes, disabling Legacy Mode might help for some but for us, with an intense use of Webhooks, it's more or less the same outcome just the problem is shifting. So one of the things would be really great, either fix the legacy mode so the "Jittering" stops or getting the actual message parser to a compatible state. (Hooks, UX)

fne007 avatar Dec 07 '22 07:12 fne007

If i may ask to give this bug some priority - we are loosing user acceptance every day and this started with Version 5.2.0.

I switched back to the old message parser yesterday to test a rendering issue reported by a user (half of our users are still on the old parser due to problems with the new parser), I noticed that in addition to the "jittering", new messages you send also appear VERY slowly. It takes at least a second before new messages appear at all, vs nearly instantly on the new parser. This was also not noticeable before 5.2.0.

ebyrne242 avatar Dec 08 '22 22:12 ebyrne242

I also can confirm that 5.4.0 made things much worse. Got many complaints after updating about bad performance and jumping texts and it took me forever to figure out it's got to do with the old parser. Fortunately, our initial issues with the new parser have been fixed (parsing of slashes) so we could switch, but no one is happy with RC anymore.

basskitty avatar Dec 15 '22 09:12 basskitty

Someone test it on 6.0.0?

itlabsinfrastructure avatar Mar 10 '23 07:03 itlabsinfrastructure