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

Java memory leak over remote desktop when screen locked/session disconnected

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: P4 P4
    • None
    • 8u51
    • deploy
    • x86
    • windows_7

      FULL PRODUCT VERSION :


      ADDITIONAL OS VERSION INFORMATION :
      Windows ver 7 32-bit

      EXTRA RELEVANT SYSTEM CONFIGURATION :
      Windows 7 PC connecting to Windows 2008 Server to launch Windows 7 RDP session

      A DESCRIPTION OF THE PROBLEM :
      I have a Java application that I am running on a computer (COMP-A). I have another computer (COMP-B) that I use to remote into COMP-A using Microsoft Remote Desktop in order to use that Java application. Both computers are running Windows 7. Whenever I am logged in, the application behaves normally using ~100 MB of memory and ~3% of my CPU. The problem is when I lock the screen, minimize or disconnect from the session, the CPU usage of said Java application immediately spikes up to ~20% and the memory leaks nonstop (I got it >700 MB but stopped it at that point as to not crash the system).

      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      1. Used Windows RDP on Machine 1 to login to Machine 2
      2. Start .jar application on Machine 2
      3. Lock screen, minimize or disconnect RDP session
      4. Memory usage will increase beyond -xmx values

      Similar to situation described here:
      http://stackoverflow.com/questions/17072967/java-application-cpu-spike-and-memory-leak-over-remote-desktop-when-screen-locke


      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      I expected the memory usage to stay within the expected bounds and behave normally
      ACTUAL -
      Memory usage exceeded -xmx values and would continue to climb, ultimately causing the PC to lock up and prevent any future RDP and local logins. PC would need to be restarted.

      REPRODUCIBILITY :
      This bug can be reproduced always.

      CUSTOMER SUBMITTED WORKAROUND :
      This does not appear to be an issue if the .jar file is launched by a local user (i.e. not through RDP).

            pardesha Pardeep Sharma
            webbuggrp Webbug Group
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: