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

Ensure that a large response does not cause OOM in RESTEasy Classic #20907

Merged
merged 1 commit into from
Oct 25, 2021

Conversation

geoand
Copy link
Contributor

@geoand geoand commented Oct 20, 2021

The idea of this change is to make the allocation of buffers only happen
when the previous write has been completed, as opposed to the previous
behavior where all the buffers where allocated upfront and could never
be deallocated if one of the writes caused an error

Fixes: #20822

The idea of this change is to make the allocation of buffers only happen
when the previous write has been completed, as opposed to the previous
behavior where all the buffers where allocated upfront and could never
be deallocated if one of the writes caused an error

Fixes: quarkusio#20822
@geoand
Copy link
Contributor Author

geoand commented Oct 21, 2021

Just as a note, I tested this with the code of the original issue and with other scenarios as well and it worked flawlessly

@geoand
Copy link
Contributor Author

geoand commented Oct 21, 2021

@stuartwdouglas can you take a look at this one?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Memory leak with Resteasy byte response?
2 participants