-
Notifications
You must be signed in to change notification settings - Fork 21
lubResults/glbResults are leaking #6437
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
Comments
Imported From: https://issues.scala-lang.org/browse/SI-6437?orig=1 |
@gkossakowski said: Martin: any estimates how long will it take you to fix it? |
@odersky said: |
although there is some information on the mailing list thread this doesn't seem like it's in a state where it's likely to progress (or to even understand whether the problem still exists) without clearer information happy to reopen if someone comes forward with clear details |
As described in http://groups.google.com/group/scala-internals/browse_thread/thread/eabcf3d406dab8b2, lubResults/glbResults are leaking. These guys are cleaned up by lub/glb, but they are also used in private methods like "def lub(ts: List[Type], depth: Int): Type", which don't clean the caches.
The text was updated successfully, but these errors were encountered: