Properly close Scala compiler classloaders in server and unit tests #3468
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously we were just leaking the
URLClassLoaders
, which would giveCodeHeap 'non-profiled nmethods' is full. Compiler has been disabled.
inscalajslib.test
and sometimes in actual usage for a long lived server. This PR ensures weZincWorkerImpl.close
actually callsURLClassLoader.close
, and also replacedval eval = UnitTester
in our test suite withUnitTester.scoped{ eval =>
so we can ensure closing of theUnitTester
andURLClassLoader
after each test completesWith this change,
scalajslib.test
no longer prints the above error. Hopefully it makes it stop happening in production as well.scalajslib.test
also drops from 7.5min to 6.5min (and drops further to 5min when I removed Scala.js 1.3.1 from the test matrix)