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

Cached Media gallery disappeared. #3832

Open
ara4n opened this issue Feb 25, 2025 · 1 comment
Open

Cached Media gallery disappeared. #3832

ara4n opened this issue Feb 25, 2025 · 1 comment
Labels
A-Media O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect

Comments

@ara4n
Copy link
Member

ara4n commented Feb 25, 2025

Steps to reproduce

  1. I opened the media gallery in Element X Internal
  2. I waited the ~30s needed to backpaginate and load a full screen of thumbnails on my Max size screen
  3. I admired the gallery
  4. Use the app a bit. I didn't open any other galleries or increase my caching particularly though.
  5. A few hours later, i reopened it, to demo how fast it now is!
  6. ...except it had forgotten everything and started over :(

Outcome

What did you expect?

Gallery to be backed by a persistent event cache, which should hang around for quite a while.

What happened instead?

Cache went boom for reasons unknown. (I'm a bit low on disk space, so might be that?)

Application version

847

Will you send logs?

Yes

@ara4n ara4n added the T-Defect label Feb 25, 2025
@Velin92 Velin92 added S-Minor Impairs non-critical functionality or suitable workarounds exist S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Occasional Affects or can be seen by some users regularly or most users rarely A-Media and removed S-Major Severely degrades major functionality or product features, with no satisfactory workaround labels Mar 3, 2025
@bnjbvr
Copy link
Member

bnjbvr commented Mar 5, 2025

Nothing looks particularly wrong or bizarre in the rageshake, on the SDK side. We have builtin resiliency, when reloading an event fails we'll clear the storage for the room it comes from; but that doesn't happen here in the attached rageshake, since we'd log an ERROR statement in this case, and I couldn't spot any related to the SDK being unable to load from storage.

For a media to disappear, we'd need the media events to disappear. So I wonder if the OS/app decided to get rid of the event cache DB in the background because storage was low; or if the persisted storage has been disabled and reenabled (doing so would clear it as well).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Media O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect
Projects
None yet
Development

No branches or pull requests

3 participants