2D resource leaks shown by Numega BoundsChecker

XMLWordPrintable

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: P4
    • None
    • Affects Version/s: 1.3.0
    • Component/s: client-libs
    • None
    • 2d
    • x86
    • windows_95

      This bug is an offshoot of 4191352: Numega BoundsChecker showing many java/jre RESOURCE LEAKS. When tested on one of the late December Kestrel-FCS builds,
      we found eight remaining leaks. This bug is for the three leaks we found that
      seem to be in the 2D code.

      allocated by CreateCompatibleDC in ..\src\win32\native\sun\awt\font\nrScalerContext.cpp(285)

      allocated by CreateFontIndirectA in ..\src\win32\native\sun\awt\font\nrScalerContext.cpp(818)

      These leaks are of similar origin: both Font and Device Context objects are
      supposed to be deleted in Win32nrScalerContext destructor. But this destructor
      is never invoked. These leaks seem to be in 2D code, so I suggest to reassign
      this leak to the 2D. By the way, this problem also includes a few nasty memory
      leaks.


      allocated by fopen in ..\src\share\native\sun\awt\font\fontmanager\fontobjects\fontObject.cpp(230)

      See Suggested Fix section about this one.

            Assignee:
            Parry Kejriwal (Inactive)
            Reporter:
            Eric Hawkes (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: