Skip to content
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

[BUG] Catchup read cause OOM #1034

Closed
superhx opened this issue Mar 27, 2024 · 0 comments
Closed

[BUG] Catchup read cause OOM #1034

superhx opened this issue Mar 27, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@superhx
Copy link
Collaborator

superhx commented Mar 27, 2024

  • Reader thread "stuck on" replacementNode
  • HashMap$Node occupies most of the memory, and these Node's incoming references are directly from the thread
  • However, the retained heap memory usage of the HashMap itself is not high

Therefore, it is suspected that the deadlock was caused by the concurrent operation of HashMap in multiple threads plus the frantic creation of Nodes within method calls causing OOM.

image
image
image
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants