netty: OutOfMemoryError on Dns Resolution

I recently upgraded to 4.1.51 to pull in a fix for #10246. However, now I get an OutOfMemory issue that seems related to the same code? We have been running netty for a few months with no OOM issues until now. I plan to downgrade netty back to 4.1.50 for now.

heap dump

Expected behavior

dns resolution

Actual behavior

OutOfMemoryError

Steps to reproduce

unfortunately i am not able to provide reproduction steps.

Minimal yet complete reproducer code (or URL to code)

Netty version

4.1.51

JVM version (e.g. `java -version`)

java version “1.8.0_212” Java™ SE Runtime Environment (build 1.8.0_212-b10) Java HotSpot™ 64-Bit Server VM (build 25.212-b10, mixed mode)

OS version (e.g. `uname -a`)

Linux 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 16 (11 by maintainers)

Commits related to this issue

Correctly limit queries done to resolve unresolved nameservers Motivation: We need limit the number of queries done to resolve unresolved nameserver as otherwise we may never fail the resolve when t... — committed to netty/netty by normanmaurer 4 years ago
Correctly limit queries done to resolve unresolved nameservers (#10478) Motivation: We need limit the number of queries done to resolve unresolved nameserver as otherwise we may never fail the res... — committed to netty/netty by normanmaurer 4 years ago
Correctly limit queries done to resolve unresolved nameservers (#10478) Motivation: We need limit the number of queries done to resolve unresolved nameserver as otherwise we may never fail the resol... — committed to netty/netty by normanmaurer 4 years ago

Most upvoted comments

@kireet ok I know what happens… Just need to think a bit about how to solve this in a proper way. stay tuned

normanmaurer on Aug 12, 2020

@kireet yeah I was not able to reproduce it as well. I will continue to debug and see if I somehow can. That said I think I will revert the Stackoverflow “fix” for now as it seems that the real reason is not really fixed which at the end then cause an OOME as we not overflow now anymore. Agree ?

normanmaurer on Aug 11, 2020

@kireet I will have a look next week as I was out for vacation

normanmaurer on Aug 2, 2020