|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
src/test/java/hudson/remoting/Bug20707Test.java
src/test/java/hudson/remoting/ClassRemotingTest.java
src/test/java/hudson/remoting/DummyClassLoader.java
src/test/java/hudson/remoting/DummyClassLoaderTest.java
src/test/java/hudson/remoting/TestEcho.java
src/test/java/hudson/remoting/util/OneShotEvent.java
http://jenkins-ci.org/commit/remoting/bd8e65cd874b863fc7d45e601da9a9267478d192
Log:
JENKINS-20707
I tried to write a test case to verify the hypothesis along the line of
https://issues.jenkins-ci.org/browse/JENKINS-20707?focusedCommentId=198755&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-198755,
but ultimately it was a dead-end.
The reason I was wrong is because ImportedClassLoaderTable maintain strong
references to all the imported classloaders, and it prevents them from
getting garbage collected. Probably for the reasons I was mentioning
in JENKINS-20707, RemoteClassLoaders never get garbage collected, so they should
never get unexported. I've spent much time trying to make the test case
work, so I'm going to commit it on the side just in case someone finds
useful in the future.
Compare: https://github.com/jenkinsci/remoting/compare/663dae9c83be^...bd8e65cd874b