Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8050213

Memory leak in javaw (reproduce-able with java console)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: P3 P3
    • None
    • 7u17
    • tools
    • windows_7

      FULL PRODUCT VERSION :
      java version " 1.7.0_17 "
      Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
      Java HotSpot(TM) Client VM (build 23.7-b01, mixed mode, sharing)

      ADDITIONAL OS VERSION INFORMATION :
      Windows 7 64-bit (using 32-bit JRE)

      A DESCRIPTION OF THE PROBLEM :
      Large amount of memory (500+ meg) usage reported in task manager for my java application. After using remote desktop.

      Heap dump show very little java heap usage (<30Meg).

      Force garbage collection shows heap memory released, but the size reported in task manager does not decrease.

      Reproduced with the java console (javaws -viewer)

      See on multiple machines with varying versions of java6 and java7.

      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :

      1. Start the javaws -viewer (memory usage around 60Meg) on machine 1
      2. Remote desktop into machine 1 from a different machine2.
      3. Minimize the rdp window. (The java console cpu usage on machine 1 increases while the rdp window is minimized and decreases when maximized.
      4. If left minimized the memory usage will grow to several hundred meg.

      Any heap dumps I've collect always show very little heap being used.

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      Remote desktop should not cause a memory leak.
      ACTUAL -
      Memory Usage should not increase.

      ERROR MESSAGES/STACK TRACES THAT OCCUR :
      I am not getting any exceptions or hotspot logs.

      However I am experiencing Windows 7 lockups/freezing that I am suspicious that is being caused by this. Machine requires a power cycle.



      REPRODUCIBILITY :
      This bug can be reproduced always.

      ---------- BEGIN SOURCE ----------
      use " javaws -viewer "
      ---------- END SOURCE ----------

      CUSTOMER SUBMITTED WORKAROUND :
      No workaround that I have found.

            Unassigned Unassigned
            webbuggrp Webbug Group
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: