Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
1.17.0, 1.15.3, 1.16.1
-
None
Description
We're observing strange IllegalStateException stacktrace output in OffHeapUnsafeMemorySegmentTest.testCallCleanerOnceOnConcurrentFree in CI like:
Feb 18 03:58:47 [INFO] Running org.apache.flink.core.memory.OffHeapUnsafeMemorySegmentTest Exception in thread "Thread-13" java.lang.IllegalStateException: MemorySegment can be freed only once! at org.apache.flink.core.memory.MemorySegment.free(MemorySegment.java:244) at java.lang.Thread.run(Thread.java:748) Exception in thread "Thread-15" java.lang.IllegalStateException: MemorySegment can be freed only once! at org.apache.flink.core.memory.MemorySegment.free(MemorySegment.java:244) at java.lang.Thread.run(Thread.java:748) Exception in thread "Thread-17" java.lang.IllegalStateException: MemorySegment can be freed only once! at org.apache.flink.core.memory.MemorySegment.free(MemorySegment.java:244) at java.lang.Thread.run(Thread.java:748)
This is caused by FLINK-21798. The corresponding system property is enabled as part of the CI run (see tools/ci/test_controller.sh:108) which makes the IllegalStateException to be thrown.
AFAIU, the intention of this test was to make sure that the cleaner logic is only called once even if the free method is called multiple times.
Attachments
Issue Links
- is caused by
-
FLINK-21798 Guard MemorySegment against multiple frees.
- Closed