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.

Sign up for GitHub

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

Jump to bottom

Memory leak from API block spamming: TX related #562

Closed
karimodm opened this issue Nov 27, 2023 · 3 comments
Closed

Memory leak from API block spamming: TX related #562

karimodm opened this issue Nov 27, 2023 · 3 comments
Assignees
@karimodm @piotrm50 @alexsporn
Milestone
v1.0.0-beta

Comments

@karimodm
Copy link
Contributor

No description provided.

@karimodm karimodm added this to the 1.0 RC milestone Nov 27, 2023
@karimodm
Copy link
Contributor Author

karimodm commented Dec 4, 2023

Identified memleak is in the gRPC -> INX StreamBuffer consumption. INX clients do not consume the stream fast enough and there is no back-pressure mechanism to throttle accumulation of data on the server side.

@karimodm
Copy link
Contributor Author

karimodm commented Dec 4, 2023

Proposed solution: sever connection to the INX client if a high water mark for the buffer is reached. Detect through some middleware.

@karimodm
Copy link
Contributor Author

Solved by iotaledger/inx-faucet#113

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@karimodm karimodm

@piotrm50 piotrm50

@alexsporn alexsporn

Labels
None yet
Projects
iota-core
Archived in project
Milestone
v1.0.0-beta
Development

No branches or pull requests
3 participants
@karimodm @piotrm50 @alexsporn