-
Bug
-
Resolution: Duplicate
-
P4
-
None
-
16.0.1, 17
When running tier2 tests on busy CI server, this happens:
TEST: jdk/dynalink/TypeConverterFactoryRetentionTests.java
TEST JDK: /home/buildbot/worker/test-jdkX-linux/build/build/linux-x86_64-server-fastdebug/images/jdk
ACTION: main -- Failed. Execution failed: `main' threw exception: java.lang.AssertionError: Should have GCd a class loader from both queues by now
REASON: Assumed action based on file name: run main TypeConverterFactoryRetentionTests
TIME: 38.445 seconds
messages:
command: main TypeConverterFactoryRetentionTests
reason: Assumed action based on file name: run main TypeConverterFactoryRetentionTests
Mode: agentvm
Agent id: 169
elapsed time (seconds): 38.445
I think this test is rather time-sensitive. I wonder if we want to extend the test time, and limit the heap size to trigger enough GCs (that would hopefully involve weak references processing)?
TEST: jdk/dynalink/TypeConverterFactoryRetentionTests.java
TEST JDK: /home/buildbot/worker/test-jdkX-linux/build/build/linux-x86_64-server-fastdebug/images/jdk
ACTION: main -- Failed. Execution failed: `main' threw exception: java.lang.AssertionError: Should have GCd a class loader from both queues by now
REASON: Assumed action based on file name: run main TypeConverterFactoryRetentionTests
TIME: 38.445 seconds
messages:
command: main TypeConverterFactoryRetentionTests
reason: Assumed action based on file name: run main TypeConverterFactoryRetentionTests
Mode: agentvm
Agent id: 169
elapsed time (seconds): 38.445
I think this test is rather time-sensitive. I wonder if we want to extend the test time, and limit the heap size to trigger enough GCs (that would hopefully involve weak references processing)?
- duplicates
-
JDK-8261483 jdk/dynalink/TypeConverterFactoryMemoryLeakTest.java failed with "AssertionError: Should have GCd a method handle by now"
- Resolved
- relates to
-
JDK-8198540 Dynalink leaks memory when generating type converters
- Resolved