Description
Do you want to request a feature or report a bug?
Bug.
What is the current behavior?
Memory leaks via Splat's MRU cache in the activation logic. The source code sets a limit of 64 activation-for-view-fetchers, but it's certainly possible to leak more instances than that. Moreover, it's not clear to me what the static cache even achieves. That is, why there is any benefit to caching activation-for-view-fetchers in the first place. Requires investigation.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
The best repro I have is in the code for my book samples. If anyone wants to look at this before I do, ping me.
What is the expected behavior?
Memory should not leak.
What is the motivation / use case for changing the behavior?
Leaking memory is bad for your health.
Which versions of ReactiveUI, and which platform / OS are affected by this issue? Did this work in previous versions of ReativeUI? Please also test with the latest stable and snapshot (http://docs.reactiveui.net/en/contributing/snapshot/index.html) versions.
7.2.
Other information (e.g. stacktraces, related issues, suggestions how to fix)