Bug Report

Describe the issue: Lemmy doom scrolling gets super laggy over 400mb memory usage. App ram usage is estimated as I can only see temporary app cache through Android dev settings when the app gets kicked into the background. Memory usage will mostly self-clear, but it takes a bit.

Steps to reproduce:

  1. Doom scrolling FTW!

Device Information

  • App Version: 1.0.316 (316)
  • Platform: android
  • OS Version: BP3A.251105.015

Modified Settings

The following settings have been changed from defaults:

  • isNotificationEnabled: 1 (default: 0)
  • alwaysShowInstance: true (default: false)
  • shouldPreloadImages: false (default: true)
  • shouldShowPageNumbers: true (default: false)
  • showFullVotes: true (default: false)
  • defaultPostSort: New (default: Active)
  • nsfwView: hide (default: blur)
  • cardType: list (default: card)
  • maxCacheSizeGB: 5 (default: 2)

(Recommend moving nsfwView preference out of a public bug report. It’s not a huge issue, but it could be a private setting for some people.)

  • kuroM
    2·
    19 days ago

    Hi, please let me know if you’re still seeing this on v318. Thank you!

    • remoteloveOP
      2·
      19 days ago

      Speed scrolled all the way to the end of the feed with no lag issues. It seems like it could have been about +100 posts. I guess the only problem is that there is an end to the feed for /all.

      Give me doom scrolling or give me death! ;)

      • kuroM
        1·
        14 days ago

        Hi, the no more posts error should be gone now as of v331. Cheers!

        • remoteloveOP
          1·
          14 days ago

          Ok, on 332 and there is still an issue. Sorry for the screenshot post, especially with data, but I exclusively use Lemmy on my phone with Connect only. (My apologies if this turns out to be a red herring.)

          I had a feeling that there is a difference between the loading behavior when using two different ways to refresh the feed. Either [Right Side Menu -> Refresh] and [Main Menu -> Click All].

          Using the Main Menu and clicking All seems to yield slightly better feed loading behavior before it hangs.

          Obviously this is non-scientific, but I reloaded feed and speed scrolled till the feed hung and recorded the last page number. It’s not an even number of test scrolls, as I just kept doing it until each test set looked about the same length:

          • kuroM
            1·
            14 days ago

            Thanks that is helpful. The logic in the app is the message is displayed when all posts in a page are filtered out so before if you went to a New sorted feed, saw posts 1-20, then waited and scrolled to page 2 but by this time there are 20 new posts then everything in page 2 would be a duplicate since we’re already showing it. That’s effectively what’s happening just over 10 or 20 pages we’re seeing every post in a next page call and there’s nothing new. I added some logic to also scan the next couple pages but it might not be enough…

            • remoteloveOP
              1·
              14 days ago

              Ah ha! I got closure so thanks for the info! https://lemmy.ca/comment/20235503

              Also, I have been hounding you with this issue for a long time. I can make a note about it (if it gets worse) after each new version release, or just leave it be. My point is if there is a better way you want me to keep checking and/or reporting this bug, let me know.

              • kuroM
                1·
                14 days ago

                I must have missed this. Are there any errors or messaging when it occurs? Just the feed stops loading?

                • remoteloveOP
                  1·
                  14 days ago

                  Just stops loading. The “no more posts” message makes it easier to see now, but prior to that, it would just stop with no errors.