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 under resource-exhausted conditions #57

Closed
jmacd opened this issue Oct 6, 2023 · 1 comment
Closed

Memory leak under resource-exhausted conditions #57

jmacd opened this issue Oct 6, 2023 · 1 comment

Comments

@jmacd
Copy link
Contributor

jmacd commented Oct 6, 2023

We have evidence that when a receiver's memory_limit setting is too low, it will respond with ResourceExhausted errors (as expected), but the condition also produces a leak such that memory accounting is quickly thrown off, and no further requests are able to be processed. It looks like failure to dereference memory under failures.
@jmacd jmacd mentioned this issue Oct 6, 2023
Merged
jmacd added a commit that referenced this issue Oct 6, 2023
@jmacd
Release v0.5.0 (#58)
20b0e89 
Since we still do not have a changelog automation, this is what is
included since v0.3.0 worthy of note:

#47
#52
#53 
#54 
#55 
#56
#57 

README improvements,
Obfuscation processor fixes.
@jmacd
Copy link
Contributor Author

jmacd commented Apr 12, 2024

Fixed.

@jmacd jmacd closed this as completed Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jmacd