Skip to content
This repository was archived by the owner on Oct 13, 2025. It is now read-only.

Conversation

@kishansr1
Copy link

Issue

While startScroll is getting called we are creating AnimationController but we are not disposing that controller.

Solution

Dispose that controller

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

  • I signed the [CLA].
  • All tests from running flutter test pass.
  • flutter analyze does not report any problems on my PR.
  • I am willing to follow-up on review comments in a timely manner.

@jamesderlin jamesderlin mentioned this pull request Apr 29, 2022
4 tasks
@jamesderlin
Copy link
Contributor

It's not the main part of this PR, but:

@xster There are going to keep being PRs and issues about nullable vs. non-nullable SchedulerBinder.instance thing until #339 (comment) is addressed.

@kishansr1
Copy link
Author

@jamesderlin I think now it can be merged.

@xster
Copy link
Member

xster commented Sep 7, 2022

Sorry for the long wait. I've created something similar at #423 to address the same issue. The fix should be on 0.3.4 on pub now.

@xster xster closed this Sep 7, 2022
@BenDevExatech
Copy link

Hi,
I came up here searching for a solution for an error : "_ScrollablePositionedListState#44259(tickers: tracking 2 tickers) was disposed with an active Ticker".

I'm on 0.3.4 version of scrollable_positioned_list package, and I still get this error.

Is this fix generic and autonomous, or should I call a dispose somewhere, as ItemScrollController class still doesn't have any dispose function?

My context: scrollable_positioned_list is used on a pop-up. If the pop-up is closed while a scrollTo event is still in progress, I get the error.

Thanks in advance for your help, tips or any solution.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants