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

Memory leak involving LazyAnnotationType #6092

Closed
scabug opened this issue Jul 17, 2012 · 2 comments
Closed

Memory leak involving LazyAnnotationType #6092

scabug opened this issue Jul 17, 2012 · 2 comments
Assignees
Labels
Milestone

Comments

@scabug
Copy link

@scabug scabug commented Jul 17, 2012

This leak manifests inside the IDE, but it stems from the way LazyAnnotationInfos are created. I have a unit test for the IDE project that can reproduce the issue (anyone typing a few minutes inside Implicits.scala would see the same thing).

In short, its call-by-name parameter becomes a field, and it never releases the closure, which in turn, through the $outer pointer, hangs on to a whole namer, on each typer run (even when the annotation is forced).

final class LazyAnnotationInfo(lazyInfo: => AnnotationInfo) extends AnnotationInfo {
    private var forced = false
    private lazy val forcedInfo = try {
     .. 
    } finally forced = true
..
@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Jul 17, 2012

Imported From: https://issues.scala-lang.org/browse/SI-6092?orig=1
Reporter: @dragos
Affected Versions: 2.10.0

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Jul 19, 2012

@scabug scabug closed this Jul 19, 2012
@scabug scabug added this to the 2.10.0-M5 milestone Apr 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.