sun.awt.windows.WInputMethod.lastFocussedComponentPeer memory leak

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: P4
    • tbd
    • Affects Version/s: 6u10
    • Component/s: client-libs

      FULL PRODUCT VERSION :
      java version "1.6.0_18"
      Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
      Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode, sharing)

      ADDITIONAL OS VERSION INFORMATION :
      Microsoft Windows XP [Verze 5.1.2600]

      A DESCRIPTION OF THE PROBLEM :
      I have an application with some dialogues. After closing them all, the last dialogue stays in the memory. I have made a dump of live objects. Eclipse memory analyser shows, that the object was hold by sun.awt.windows.WInputMethod.lastFocussedComponentPeer reference.

      I think this reference should be weak.

      I have not tried it, but I guess the same problem is with JFrame.

      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      Make a dialogue:
      JDialog d;
      d = new JDialog(...);
      d.setVisible(true);
      d.dispose();

      Make a heap dump and analyse it.

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      The dialogue should be GC'ed.
      ACTUAL -
      The dialogue is in the heap.

      REPRODUCIBILITY :
      This bug can be reproduced always.

            Assignee:
            Naoto Sato
            Reporter:
            Igor Nekrestyanov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Imported:
              Indexed: