-
Bug
-
Resolution: Unresolved
-
P3
-
25
-
None
-
In Review
The fix for stale values from ClassValue::remove in JDK-8351045 breaks backward compatibility and contracts that calls to remove from computeValue should be no-op. After investigation, a better solution is to update the remove implementation to force recomputation only on other threads.
- caused by
-
JDK-8351045 ClassValue::remove cannot ensure computation observes up-to-date state
-
- Closed
-
- csr for
-
JDK-8352433 Behavioral updates for ClassValue::remove
-
- Provisional
-
- relates to
-
JDK-7153157 ClassValue.get does not return if computeValue calls remove
-
- Resolved
-
- links to
-
Review(master) openjdk/jdk/24043