Bug 1442162 - Using jdb triggers OOME on the debugged application
Using jdb triggers OOME on the debugged application
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: java-1.8.0-openjdk (Show other bugs)
7.0
x86_64 Linux
high Severity high
: rc
: ---
Assigned To: Andrew John Hughes
Jan Kepler
: Reopened, ZStream
Depends On: 1284948
Blocks:
  Show dependency treegraph
 
Reported: 2017-04-13 13:10 EDT by Jaroslav Reznik
Modified: 2017-04-20 22:11 EDT (History)
11 users (show)

See Also:
Fixed In Version: java-1.8.0-openjdk-1.8.0.131-2.b11.el7_3
Doc Type: Bug Fix
Doc Text:
When a method is called using the Java Debug Wire Protocol (JDWP) "invokeMethod" command in a target Java virtual machine, JDWP creates global references for every Object that is implied in the method invocation, as well as for the returned argument of the reference type. Previously, the global references created for such arguments were not collected (deallocated) by the garbage collector after "invokeMethod" finished. This consequently caused memory leaks, and because references to such objects were never released, the debugged application could be terminated with an Out of Memory error. This bug has been fixed, and the described problem no longer occurs.
Story Points: ---
Clone Of: 1284948
: 1443684 (view as bug list)
Environment:
Last Closed: 2017-04-20 22:11:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Icedtea Bugzilla 3313 None None None 2017-04-13 13:10 EDT
openjdk bug system JDK-8153711 None None None 2017-04-13 13:10 EDT

  None (edit)
Description Jaroslav Reznik 2017-04-13 13:10:02 EDT
This bug has been copied from bug #1284948 and has been proposed
to be backported to 7.3 z-stream (EUS).
Comment 16 errata-xmlrpc 2017-04-20 22:11:16 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:1108

Note You need to log in before you can comment on or make changes to this bug.