Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reuse classloaders of the same Scala version #37

Closed
jvican opened this issue Nov 16, 2017 · 2 comments
Closed

Reuse classloaders of the same Scala version #37

jvican opened this issue Nov 16, 2017 · 2 comments
Assignees
Labels
bug A defect or misbehaviour. performance

Comments

@jvican
Copy link
Contributor

jvican commented Nov 16, 2017

We're potentially classloading the Scala universe twice, one in ScalaInstance and another one in the ClassLoaderCache created internally by ZincUtil.scalaCompiler. We should unify these two so that we construct the classloader cache ourselves, we share it across the two different use sites, and we pass it in explicitly to create AnalyzingCompiler.

@jvican jvican self-assigned this Nov 22, 2017
@jvican jvican added the bug A defect or misbehaviour. label Nov 22, 2017
@jvican jvican added this to the Bloop 0.1 milestone Nov 22, 2017
@jvican
Copy link
Contributor Author

jvican commented Nov 23, 2017

This is actually not happening right now, the classloaders in scala instance are not forced because we don't use actualVersion in bloop. But we could use it in the future, so in that case it's important we reuse classloaders accross all the instance.

@jvican
Copy link
Contributor Author

jvican commented Nov 29, 2017

Now we do use actualVersion. The good thing is that our caching at the scala instance level prevents us from deduplicating classloaders. I'm closing this since it's not necessary anymore.

@jvican jvican closed this as completed Nov 29, 2017
tpasternak pushed a commit to tpasternak/bloop that referenced this issue Dec 23, 2021
Seems 1.0.5 has issues on Windows…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A defect or misbehaviour. performance
Projects
None yet
Development

No branches or pull requests

2 participants