Skip to main content

UI Slowdown when reaching media feed

Version: 0.9.0 (build: 42)

Device model: BRAVIA 4K UR2

Device RAM: 2301 MB

The entire UI feels very responsive, even on 'High' preset given the specs of the Sony Bravia televisions. However, once I reach the external media feeds (ie Netflix or Amazon Prime) the UI freezes for a second or sometimes even two.

Perhaps it is possible to fetch this content on a background thread or asynchronously (if not done already). I have no way to profile the application to see what slows it down, but I suspect the Media Feed fetch requests blocking the main thread, halting the UI rendering task.

Current behaviour

Reaching the bottom of the Plex suggestions shows the external sources which greatly impacts performance.

Expected behaviour

Showing external Media Feeds should not impact performance any other than showing the Plex suggestions.

Status: Completed3 comments

Log in to comment and vote

Comments3

  • Paul Dhaliwal changed status to Completed
    •

    Aug 15, 2024

    Fixed via a new image caching mechanism and will be available in v1.

  • Paul Dhaliwal

    •

    Jun 28, 2024

    Thanks for the report! Actually no data is being fetched externally as you already scroll through the feed. If it's showing on the home feed, it's already cached in the local database.

    It may have to do with the images being cached for the first time in those rows, however. Can you confirm that the behaviour persists even if all those images have been loaded before? I may look into loading those images differently.

    If you can, would you be able to attach a small video showing the issue as well. Technically speaking I believe those rows should actually load more smoothly than the regular Plex rows.

    • Ricardo Snoek-Valkenburg

      •

      Jun 28, 2024

      Paul Dhaliwal The behaviour does not seem to persist indeed. I guess the feed was being cached only once I have reached that part of the page. But it is hard for me to validate the issue without resetting the app cache itself.

      If I'm required to do so I can do this to validate this is indeed the issue.