this post was submitted on 29 Dec 2025
6 points (100.0% liked)

Connect for Lemmy App

3594 readers
12 users here now

A community for the mobile app Connect for Lemmy.

Links

founded 2 years ago
MODERATORS
 

Bug Report

Describe the issue: Just feed scrolling lag. I noticed it this time after page 20, with about 1Gb in process memory. (It seems to take a bit more scrolling now to see issues.)

Steps to reproduce:

  1. Have no life
  2. Leverage online media as a form of social acceptance
  3. Keep doom scrolling.

Device Information

  • App Version: 1.0.319 (319)
  • 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)
  • shouldShowPageNumbers: true (default: false)
  • showFullVotes: true (default: false)
  • defaultPostSort: New (default: Active)
  • nsfwView: hide (default: blur)
  • cardType: list (default: card)
  • maxCacheSizeGB: 5 (default: 2)
top 4 comments
sorted by: hot top controversial new old
[–] kuro_neko@lemmy.ca 3 points 3 weeks ago (1 children)

Thanks for the report, I'll be honest I've never gotten to page 20 before. I'll take a look tonight. Cheers!

[–] remotelove@lemmy.ca 1 points 3 weeks ago (1 children)

Lol! I just scroll really fast, it seems. Seriously though, if I skip Lemmy for a few days, it's kinda easy to get that deep into unread posts.

In this case, I noticed a bit of lag starting at around page 10, so I just pushed the app harder than normal to see if I could make it worse.

[–] kuro_neko@lemmy.ca 2 points 3 weeks ago (1 children)

Hi, I think the scroll lag you were seeing should be resolved on the latest beta version (v322). Before some things were being stored in memory that should have been cleared.

[–] remotelove@lemmy.ca 1 points 3 weeks ago

Lag is gone, thank you. I got to around page 46 on my longest attempt.

The feed can still stop at times, and when it does, it's around page 10 or so. I'll take a peek at the network traffic later to see if there is something cutting the network traffic. (I might see a RST or something from an intermediate.. dunno.)