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

potential deadlock and performance issue in freeing strike resources with D3D pipeline

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • P4
    • 7
    • 7
    • client-libs
    • 2d
    • b77
    • generic
    • generic

    Backports

      Description

        The 6u10+ JDK D3D pipeline needs to free glyphs on the Toolkit thread
        (see bug 6705443 for more details). This means having to switch
        over to that thread from the disposer thread, one time for each strike.
        And because this needs to happen synchronously, and involves calling
        into native code to do so, it would seem relatively expensive.
        This hasn't been seen as a performance problem in most apps but an
        app that generates many (as in tens of thousands) strikes over
        a short period of time, it can show up in measurements.

        In addition there's a call to dispose() in Font2D.java.
        When the 6u10 code was added this became a source of potential deadlock.

        Attachments

          Issue Links

            Activity

              People

                prr Philip Race
                prr Philip Race
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: