rive-app / rive-app/rive-flutter

[Flutter Web] Memory leak: Infinite memory growth with looping animation even after stopping

Open
#628 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dart
Stars
1.5k
Forks
240
PR merge metrics
No merged PRs in 30d

Description

Submission checklist
  • I have confirmed the issue is present in the latest version of the rive Flutter package
  • I have searched the documentation and forums and could not find an answer
  • I have searched existing issues and this is not a duplicate
Description

I am experiencing a significant memory leak when using rive-flutter on the Flutter Web platform.
When a looping animation is played, the memory usage increases infinitely over time. Crucially, even if the animation is stopped or the controller is disposed, the memory is not released, and the usage remains high.

Reproduction steps / code

No response

Upload your reproduction files / stack trace

No response

Source .riv / .rev file

No response

Screenshots / video

No response

Rive Flutter package version

0.13.20, 0.14

Flutter version

dart: ">=3.11.0 <4.0.0"
flutter: ">=3.41.0"

Device

Chrome, Edge

OS version

Mac OS, Windows 11

Additional context

No response

Contributor guide

No contributing guide indexed for this repository

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

No reproduction files, source asset, stack trace, or project entry point are provided. Start by creating a minimal Flutter Web reproduction using rive-flutter 0.13.20 or 0.14 in Chrome or Edge, then inspect memory while a looping animation runs and after it is stopped or disposed. Done means the leak is isolated and memory is released after disposal, with a regression check if the project provides a suitable test location.

Written by the indexing model from the issue text.

Assessment

Tech stack
dart, flutter
Domain
performance, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.