I've created https://bugs.openjdk.java.net/browse/JDK-8029595 to track
some clean up in this area.
regards,
Sean.
On 04/12/2013 16:44, Mandy Chung wrote:
On 12/4/2013 7:51 AM, Alan Bateman wrote:
On 04/12/2013 15:44, Seán Coffey wrote:
Recent jdk8 builds seem to be more ambitious on the GC f
I see this was pushed already. Good, quick work guys!
Yes, there are a couple other RMI test failures caused by aggressive GC of
loggers (or possibly other objects). I know the Hotspot folks have filed a
couple already. But we should keep an eye out for them.
s'marks
On 12/4/13 7:44 AM, Seán
On 12/4/2013 7:51 AM, Alan Bateman wrote:
On 04/12/2013 15:44, Seán Coffey wrote:
Recent jdk8 builds seem to be more ambitious on the GC front. It
turns out that we've no strong reference for the Logger being created
in this testcase and it's collected before use.
Thanks Sean, I've seen this f
On 04/12/2013 15:44, Seán Coffey wrote:
Recent jdk8 builds seem to be more ambitious on the GC front. It turns
out that we've no strong reference for the Logger being created in
this testcase and it's collected before use.
Thanks Sean, I've seen this fail many times recently due to the logger
b
Recent jdk8 builds seem to be more ambitious on the GC front. It turns
out that we've no strong reference for the Logger being created in this
testcase and it's collected before use.
Verified that test now passes.
suggested fix :
diff -r 28ca338366ff test/sun/rmi/runtime/Log/checkLogging/Chec
