You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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).
The text was updated successfully, but these errors were encountered: