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

Relaunch should not repeat update checks for eager resources

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P3 P3
    • 8
    • 7u10
    • deploy
    • b52
    • generic
    • generic
    • Verified

        Currently if application or applet require relaunch, we already performed update check and downloaded all eager resources. In the relaunched VM, we continue to check for update of these resources which would impact application total startup time.

        We could do better, by either carry over update tracker state or simply say "eager update should have been done before relaunch do not retry it in the relaunched JVM"

              nam Nam Nguyen (Inactive)
              nam Nam Nguyen (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: