-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unread count goes from zero through the roof after restarting the app #25479
Comments
I've noticed this primarily on DMs, ftr |
Can't reproduce the rapidly rising unread count anymore as of this morning. Travis had posted to the main timeline in the room to clear his stuck notification which might be related. |
I can also see this problem from time to time. That happens rarely. |
This issue is a duplicate of #25450 Digging through the logs I can find the following exception
The last event in the main live timeline is a reaction that belongs to a thread. Your accumulated read receipt refers to an older event. |
@gsouquet I've definitely seen this happen when it's not a reaction in the main timeline. It appears others have as well (rageshakes hopefully inbound on this). |
If this is a release blocker and a duplicate of #25450, should the other issue become a release blocker? |
Yes, good catch. Have made it so. We've internally been treating it like this already. |
I'm still seeing this on nightly 2023060102 which includes matrix-org/matrix-js-sdk#3427. Have logged https://github.com/matrix-org/element-web-rageshakes/issues/21713. Reopening this but taking off the release blocker label because the general stuck notification experience is much better on this version. |
If it helps, I'm experiencing this when clicking on 'mark as read'. It's happened to me twice in the last few days but I wasn't able to rageshake. Will do so next time. |
The latest Element Nightly 2023062901 seems to go through the roof and back to zero by itself, if it helps. |
Not sure if it's actually the same issue, but I've started experiencing this randomly on Element Web v1.11.35 every other day now. I click on a room that has an (actual) unread message, and sometimes it just starts marking thee last couple hundred messages or so as unread in that room |
Yes, that sounds exactly like what I'm seeing, too |
There is a reproducer in https://github.com/matrix-org/element-web-rageshakes/issues/22619, with videos to show it in action, and notification debug information for the room where the issue is happening |
See #26475 for this; I just created it. |
I can reproduce this consistently with Element Nightly version: 2023112101 Crypto version: Olm 3.2.15. Steps:
Bonus: scroll up to get even more unreads |
I'm experiencing the same issue as described by davidegirardi #25479 (comment) with Element version: 1.11.51 Crypto version: Olm 3.2.15 |
@salvador-diaz that's an ancient version (with known security vulnerabilities no less). Please upgrade. I haven't encountered this behaviour in months. |
@davidegirardi my bad 😅️, upgraded to 1.11.79 and problem solved. Thanks |
Steps to reproduce
Outcome
What did you expect?
Lots of messages are marked unread
What happened instead?
No unread count in the room
Operating system
macOS
Application version
Element Desktop nightly
How did you install the app?
No response
Homeserver
element.io
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: