Open localhost:8080 in Safari and record a Memory and JavaScript Allocations timeline for a minute while navigating between http://localhost:8080 and http://localhost:8080/notes/add
Experience that the size of memory grows steadily, while garbage collection (S) has next-to-no effect:
Screenshot from Chrome:
I experience the same in my ember app when trying out glimmer-apollo (a lot more data leads to eventual crashes). Initially thought it was because I did some data fetching in controllers, but being able to reproduce with examples/glimmerx makes me question whether the hungry memory consumption is inherent to glimmer-apollo?
Or is the expected behavior that all results are retained in memory until a manual garbage collection of the InMemoryCache?
Steps to reproduce:
examples/glimmerx
app withyarn start
localhost:8080
in Safari and record a Memory and JavaScript Allocations timeline for a minute while navigating betweenhttp://localhost:8080
andhttp://localhost:8080/notes/add
Screenshot from Chrome:
I experience the same in my ember app when trying out glimmer-apollo (a lot more data leads to eventual crashes). Initially thought it was because I did some data fetching in controllers, but being able to reproduce with
examples/glimmerx
makes me question whether the hungry memory consumption is inherent to glimmer-apollo?Or is the expected behavior that all results are retained in memory until a manual garbage collection of the InMemoryCache?