You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
zizhong
pushed a commit
to zizhong/rest.li
that referenced
this issue
Apr 2, 2021
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: