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

Revisit implementation of memory session

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • P3
    • Resolution: Fixed
    • 19
    • 19
    • core-libs
    • None

    Backports

      Description

        The addition of a new exception kind in the liveness check (WrongThreadException) has introduced some asymmetry in the code, as we try not to allocate exceptions in the fast path, but we currently only do that for IllegalStateException.

        Furthermore, with the addition of non closeable views, the implementation of memory sessions has not aged well - some mechanism has been added (Scoped::sessionImpl) to obtain the "true" session hidden behind a view (as we need this session for the liveness check in ScopedMemoryAccess). A better implementation is possible, by factoring stateful parts into a common State class that can be used by all sessions (including views).

        Attachments

          Issue Links

            Activity

              People

                mcimadamore Maurizio Cimadamore
                mcimadamore Maurizio Cimadamore
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: