-
Bug
-
Resolution: Fixed
-
P3
-
19
-
None
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8290182 | 20 | Maurizio Cimadamore | P3 | Resolved | Fixed | b06 |
JDK-8291412 | 19.0.2 | Maurizio Cimadamore | P3 | Resolved | Fixed | b01 |
JDK-8291255 | 19.0.1 | Maurizio Cimadamore | P3 | Resolved | Fixed | b04 |
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).
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).
- backported by
-
JDK-8290182 Revisit implementation of memory session
-
- Resolved
-
-
JDK-8291255 Revisit implementation of memory session
-
- Resolved
-
-
JDK-8291412 Revisit implementation of memory session
-
- Resolved
-
(1 links to)