Skip to content

Conversation

@alexmoore
Copy link
Contributor

Netty 4.1.3 has a regression where memory can balloon with high-concurrency use cases (us).

4.1.4 fixes that regression. http://netty.io/news/2016/07/27/4-0-40-Final-4-1-4-Final.html

@jplock
Copy link
Contributor

jplock commented Sep 1, 2016

The latest is 4.1.5, should we go with that version instead?

@lukebakken
Copy link
Contributor

Is there a change log available for netty? I can't seem to find anything comprehensive.

@alexmoore
Copy link
Contributor Author

@alexmoore
Copy link
Contributor Author

And here's the original memory issue in 4.1.3: https://groups.google.com/forum/#!msg/netty/wJ-fzhsSMx8/aEXf8z5SBAAJ

@lukebakken
Copy link
Contributor

Ah, thanks. Seems like that's the version that should be used (4.1.5)

@lukebakken
Copy link
Contributor

👍 tests pass locally

@alexmoore alexmoore changed the base branch from develop to 2.0.x-develop September 1, 2016 15:39
@alexmoore alexmoore merged commit 7641734 into 2.0.x-develop Sep 1, 2016
@alexmoore alexmoore deleted the CLIENTS-978-Netty-regression branch September 1, 2016 15:44
@alexmoore alexmoore changed the title Bump Netty to 4.1.4 Bump Netty to 4.1.5 Sep 1, 2016
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.

4 participants