-
Notifications
You must be signed in to change notification settings - Fork 547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TimingKey Memory Leak #587
Labels
bug
For reporting bugs or issuing bug fixes
Comments
zizhong
pushed a commit
to zizhong/rest.li
that referenced
this issue
Apr 2, 2021
zizhong
pushed a commit
to zizhong/rest.li
that referenced
this issue
Apr 2, 2021
zizhong
pushed a commit
to zizhong/rest.li
that referenced
this issue
Apr 12, 2021
zizhong
pushed a commit
to zizhong/rest.li
that referenced
this issue
Apr 29, 2021
zizhong
pushed a commit
to zizhong/rest.li
that referenced
this issue
May 3, 2021
nizarm
pushed a commit
that referenced
this issue
May 3, 2021
lesterhaynes
pushed a commit
to lesterhaynes/rest.li
that referenced
this issue
May 14, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, TimingKey is implemented with a concurrent hashmap. TimingKey currently only provides registerKey to add an entry to the hashmap.
Each HTTPClient will create several different filters. Each filter will trigger registerKey several times.
There is no mechanism to reclaim the memory after the filters are unreachable.
If an app keeps creates new HTTPClients, the issue becomes more obvious.
The text was updated successfully, but these errors were encountered: