Repository navigation
docs: say that a local variable keeps its object reachable until the method returns - #93
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
There was a problem hiding this comment.
This PR updates docs/support.md to document that java-web keeps objects reachable via local variables until the method returns or the variable is overwritten, unlike HotSpot which can drop them after last use. This explains a known test failure in ReachabilityFenceTest.
review-bot, model nvidia/nemotron-3-ultra-550b-a55b:free, verdict approve
What this changes
docs/support.md now says that a local variable keeps its object reachable until its method returns or the slot is overwritten. HotSpot's compiled code can drop the object after the variable's last use, so on java-web such an object is cleared or finalized later. This is why
java/lang/ref/ReachabilityFenceTest.javafails. The other gaps that keep OpenJDK tests failing are already in the same file: file mappings larger than native memory, TCP urgent data, and a class loader with afinalize()on a reference cycle.Tests
Docs only.