Skip to content
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

UTDs not retried when key arrives at almost the same time #4202

Open
Tracked by #245
andybalaam opened this issue Jan 27, 2025 · 2 comments
Open
Tracked by #245

UTDs not retried when key arrives at almost the same time #4202

andybalaam opened this issue Jan 27, 2025 · 2 comments
Labels
A-E2EE T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@andybalaam
Copy link
Member

andybalaam commented Jan 27, 2025

Steps to reproduce

See this rageshake: https://github.com/element-hq/element-x-android-rageshakes/issues/4076

The logs in the receiver side show a pattern like this:

2025-01-20T15:46:43.519041Z Failed to decrypt a room event
... (9 more Failed to decrypt)
2025-01-20T15:46:46.398276Z Failed to decrypt a room event
2025-01-20T15:46:46.407885Z Received a new megolm room key
2025-01-20T15:46:46.418528Z Failed to decrypt a room event
.. (2 more Failed to decrypt)

So the megolm key arrived at almost the same moment as the events.

There is no mention of "Retrying decryption" anywhere in the receiver logs.

I am wondering whether the async task pulling from room_keys_received_stream() might have retried decryption too early, before the incoming batch of events was finished processing?

@andybalaam
Copy link
Member Author

Could be caused by event cache work?

@andybalaam
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE T-Defect Something isn't working: bugs, crashes, hangs and other reported problems
Projects
None yet
Development

No branches or pull requests

1 participant