Skip to content

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

Closed
scabug opened this issue Sep 27, 2012 · 4 comments
Closed

lubResults/glbResults are leaking #6437

scabug opened this issue Sep 27, 2012 · 4 comments

Comments

@scabug
Copy link

scabug commented Sep 27, 2012

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.

@scabug
Copy link
Author

scabug commented Sep 27, 2012

Imported From: https://issues.scala-lang.org/browse/SI-6437?orig=1
Reporter: @xeno-by

@scabug
Copy link
Author

scabug commented Sep 27, 2012

@gkossakowski said:
Just to make it clear this is an issue with compiler itself and not reflection. That's why it's marked blocker.

Martin: any estimates how long will it take you to fix it?

@scabug
Copy link
Author

scabug commented Sep 29, 2012

@odersky said:
I think it's better to leave it. It's after all not the compiler itself that would leak. The fix is not completely trivial. So I'd prefer to leave it for 2.10.1

@scala scala deleted a comment from scabug Feb 14, 2025
@scala scala deleted a comment from scabug Feb 14, 2025
@scala scala deleted a comment from scabug Feb 14, 2025
@scala scala deleted a comment from scabug Feb 14, 2025
@scala scala deleted a comment from scabug Feb 14, 2025
@SethTisue
Copy link
Member

SethTisue commented Feb 14, 2025

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

@SethTisue SethTisue closed this as not planned Won't fix, can't repro, duplicate, stale Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants