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

Navigating between rooms containing E2EE images breaks Firefox spectacularly #11267

Closed
ara4n opened this issue Oct 30, 2019 · 4 comments
Closed

Comments

@ara4n
Copy link
Member

ara4n commented Oct 30, 2019

If you create an E2E room in a big account with a few large (~3-4MB) images in it and start navigating back and forth, Firefox particularly grinds to a spectacular halt with ~20s garbage collections (on my top-end MBP).

Screenshot 2019-10-30 at 19 00 26

It feels like we might be going and undecrypting the original file (even if we don't view it) rather than just the smaller thumbnails?

@ara4n ara4n added the T-Defect label Oct 30, 2019
@ara4n ara4n changed the title Navigating between E2EE images breaks Firefox spectacularly Navigating between rooms containing E2EE images breaks Firefox spectacularly Oct 30, 2019
@ara4n
Copy link
Member Author

ara4n commented Oct 30, 2019

given that clicking on a thumbnail instantly displays the fullres image without downloading anything, it definitely feels like we are incorrectly loading the fullres encrypted images somewhere rather thabn just the thumbnails.

@ara4n
Copy link
Member Author

ara4n commented Nov 1, 2019

This is currently making my riot/web literally unusable due to the 20s GCs on firefox (after I stupidly sent a 11MB encrypted image into a room).

The problem is that MImageBody decrypts both the thumbnail and the actual target on mount, and apparently always has done. Instead, need to delegate decrypting the target until something actually tries to get at the content URL.

@ara4n
Copy link
Member Author

ara4n commented Nov 1, 2019

...which is relatively tricky, as we currently need the content URL to render the download link of the image, unless we lazyload that in, which would feel quite flakey. probably better to avoid providing a download link from the thumbnail entirely, and instead only from the lightbox.

@kittykat
Copy link
Contributor

kittykat commented Dec 1, 2021

I'm going to close this issue for now as we cannot reproduce it. Please reopen if you are still experiencing it.

@kittykat kittykat closed this as completed Dec 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants