Possible memory leak about flutter_reactive_value HOT 7 CLOSED

OK, I found a way to do this efficiently using Expando. ReactiveValueNotifier is now a subclass though, not an extension. Published in 2.0.0. Thanks for the report!

from flutter_reactive_value.

Does its fixed now? No memory leaks?

from flutter_reactive_value.

@alwerr There should be no memory leaks now, correct. But it is hard to test this, because testing this requires the garbage collector to be triggered.

from flutter_reactive_value.

Ok. thanks, great package, @lukehutch do you still use it?

from flutter_reactive_value.

I actually don't use it anymore, because I have much more complex needs for ValueNotifiers now, such as defining a ValueNotifier that reactively responds to changes in multiple other ValueNotifiers (allowing a reactive DAG of notifies to be built). Also I use my other package, Persistent ValueNotifier a lot, and that no nonger works together with ReacrltiveValueNotifier as of version 2.0. So at this point I have about 8 different subclasses of ValueNotifier built for different purposes, and I just use them with ValueListenableBuilder, or my own alternative to that class which I also built (but haven't published yet).

The simplest thing to use today in general is simply ValueNotifier with ValueListenableBuilder, since both are included in Flutter.

from flutter_reactive_value.

Persistent ValueNotifier looks really helpful, so I guess I would use ValueNotifier with ValueListenableBuilder too, are they working in stateless widget too? like in this package?

from flutter_reactive_value.

Yes, ValueListenableBuilder is a stateful widget that rebuilds when the ValueNotifier it is watching changes. It can be used inside any widget (including a stateless widget). It's very simple to use. And PersistentValueNotifier works perfectly with it.

from flutter_reactive_value.