LemmyNet / LemmyNet/jerboa

Closing and reopening partially loaded image leads to multiple parallel downloads

Open
#2,158 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Kotlin
Stars
1.3k
Forks
175
Avg merge
6d 22h
Merged PRs (30d)
9

Description

Jerboa Version

0.0.87-fdroid

Android Version + Phone

LineageOS 23.2 (Android 16), Pixel 4a

Describe The Bug

When opening images on a slow connection or from a slow instance, the download progress bar on the top slowly fills. When I go back before the image fully loads and open the image again, the progress bar now jumps between the previous progress and the new one, both slowly going forward.
It looks like the image is now being downloaded two times in parallel. This can be stacked multiple times.

See also this screencast

https://github.com/user-attachments/assets/30bc55d2-5682-4aa5-a0b4-2b169823599e

To Reproduce
  1. Open image over slow connection.
  2. Let it load a bit, e.g. halfway
  3. Press back
  4. Open the image again
  5. The progress bar now jumps between two states
  6. Repeat at step 2 to add more states.
In the case of a crash or when relevant include the logs

Apart from log entries like these, there is no debug log regarding image downloads

06-28 07:13:58.814 20264 20264 D jerboa  : got to community screen
06-28 07:14:37.710 20264 20264 D jerboa  : got to community screen

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in Jerboa 0.0.87 on Android by reopening a partially loaded image over a slow connection and confirming that progress states accumulate. Trace the image-loading lifecycle across back navigation and reopening; done when reopening no longer leaves parallel downloads or competing progress updates, and the reproduction steps pass without regressions.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.