PathFiller obj. in java2d needs Disposer mechanism

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P4
    • None
    • Affects Version/s: 1.4.0, 5.0
    • Component/s: client-libs
    • None
    • 2d
    • generic
    • generic, solaris_8

      At present PathFiller depends on finalizer to dispose native memory. This
      causes it to depend on GC in turn, which is becoming a overhead. In some scenario, finalizers were slower in action to dispose the native memory, causing
      an impression of memory leak to the end user. Disposer mechnism takes a good care in disposing the native memory. Hence it's advisable to implement disposer
      mechanism to PathFiller.

            Assignee:
            Jim Graham
            Reporter:
            Harsha Godugu (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: