shareReplay default behavior lead to Memory Leak after long time running #7471
snowwolfjay
started this conversation in
Report issues other than bug
Replies: 1 comment 1 reply
-
I just hope there's a ConfigObject like thing to know and control default values |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
shareReplay parse params use follow code:
which default bufferSize and windowTime is Infinity , which is default danger design, and hard to find out when develop or e2e/unit test. I notice these because my app (large screen ) crash after longtime running (after half month) and need restart. After rounds of optimization, i finally find this .
So I hope there are some notice there , include docs and commits, or provide some globalConfig things to control.
following is the params description:
Default should be Infinity Buffersize and windowTime
Beta Was this translation helpful? Give feedback.
All reactions