miru-project/miru-app

Potential Memory Leak on Windows 11?

Open

#335 opened on Jul 21, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Dart (5,505 stars) (236 forks)batch import
help wanted

Description

Brief summary

I ran the App. 136 Mb at 11.41am 478.9 Mb at 11.45am 1.4 Gb at 12.26

Played 1 video for 2 mins

after spending some time 1hr more approx. ( without playing any vids) 6.7Gb at 1.18pm

closed the app.

I noticed when the app is in Foreground (not minimized) it keeps hogging more memory.

Steps to reproduce

  1. open Task manager
  2. run the app
  3. check memory usage

Miru version

1.8.1

Device

Windows 11, Dell Laptop

Acknowledgements

  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
  • If this is an issue with a extension, I should be opening an issue in the extension repository.

Contributor guide

Tech stack
dartflutter
Domain
desktopperformance
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Flutter development environmentfamiliarity with memory profiling tools
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate memory usage using Flutter DevTools memory profiler. Look for common memory leak patterns such as unclosed streams, improper disposal of controllers, or retaining large objects in the widget tree. The issue describes memory growth when the app is in the foreground, so focus on active screen rendering and state management. Check for leaks in video player components and any cached data that is not released.