Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8034666 | 7u65 | Ivan Gerasimov | P3 | Resolved | Fixed | b01 |
JDK-8022641 | 7u60 | Ivan Gerasimov | P3 | Closed | Fixed | b01 |
JDK-8023189 | 6-pool | Ivan Gerasimov | P4 | Closed | Won't Fix |
FULL PRODUCT VERSION :
java version " 1.7.0 "
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Server VM (build 21.0-b17, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Linux ubuntu 2.6.38-10-generic,
ARM linux kernel 2.6
A DESCRIPTION OF THE PROBLEM :
Running some methods on NetworkInterface object causes memory leaks. This methods are at least isUp() and isLoopback(). I've observed it in both standard and embeded JRE. I've checked it also in OpenJDK, but no memory leaks were found there. I guess the problem is somewhere in libnet.so.
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
ArrayList<NetworkInterface> tmpInterfaces = Collections.list(NetworkInterface.getNetworkInterfaces());
for (NetworkInterface iface : tmpInterfaces) {
iface.isLoopback();
iface.isUp();
}
//memory leak is easy to observe if you run this in a loop
---------- END SOURCE ----------
java version " 1.7.0 "
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Server VM (build 21.0-b17, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Linux ubuntu 2.6.38-10-generic,
ARM linux kernel 2.6
A DESCRIPTION OF THE PROBLEM :
Running some methods on NetworkInterface object causes memory leaks. This methods are at least isUp() and isLoopback(). I've observed it in both standard and embeded JRE. I've checked it also in OpenJDK, but no memory leaks were found there. I guess the problem is somewhere in libnet.so.
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
ArrayList<NetworkInterface> tmpInterfaces = Collections.list(NetworkInterface.getNetworkInterfaces());
for (NetworkInterface iface : tmpInterfaces) {
iface.isLoopback();
iface.isUp();
}
//memory leak is easy to observe if you run this in a loop
---------- END SOURCE ----------
- backported by
-
JDK-8034666 Memory leak in NetworkInterface methods ex. isUP(), isLoopback()
-
- Resolved
-
-
JDK-8022641 Memory leak in NetworkInterface methods ex. isUP(), isLoopback()
-
- Closed
-
-
JDK-8023189 Memory leak in NetworkInterface methods ex. isUP(), isLoopback()
-
- Closed
-
- duplicates
-
JDK-8022796 Backport: Memory leak in NetworkInterface methods ex. isUP(), isLoopback()
-
- Closed
-
-
JDK-8022696 Memory leak in NetworkInterface native methods
-
- Closed
-