-
-
Notifications
You must be signed in to change notification settings - Fork 15.8k
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
JVM crash on heavy load #2950
Comments
one more thing whenever it runs on native epoll the error would be at
|
@jknair could you try to run with |
@jknair ok I may have an idea... stay tuned. |
hey ran the app disabling unsafe and used nio event loops and no crashes in the last 12 hours |
@normanmaurer keeping unsafe turned off we are hitting FULL GC's !!! |
Motivation: Before we missed to check if a buffer was released before we return the backing byte array or memoryaddress. This could lead to JVM crashes when someone tried various bulk operations on the Unsafe*ByteBuf implementations. Modifications: Always check if the buffer is released before all to return the byte array and memoryaddress. Result: No more JVM crashes because of released buffers when doing bulk operations on Unsafe*ByteBuf implementations.
@jknair let me close this and please re-open if you still encounter the problem with latest code |
using netty master @ c40b0d2 . We are seeing recurring JVM crashes on heavy loads. Similar issue
#1117 . We saw this using both epoll and nio eventloops.
System info :
java version "1.8.0_20"
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode)
Linux testbox # 1 SMP Debian 3.14.15-2 (2014-08-09) x86_64 GNU/Linux
Any workaround how to avoid this ?
The text was updated successfully, but these errors were encountered: