Re: Memory leak in LinkedHasMap and LinkedHashSet
Rex Kerr <[email protected]>
| Newsgroups | gmane.comp.lang.scala |
|---|---|
| Message-ID | <CAP_xLa1MWGTy1hLnnbLkay98tXM1XaEMNfS62+aeEKOifcXsKg@mail.gmail.com> |
Sounds like a bug to me. Please file a bug report at issues.scala-lang.org! If you assign it to me, I'll most likely fix it by 2.11.6, if it is a simple matter of setting those to null. --Rex On Thu, Jan 15, 2015 at 2:34 AM, Jacek <[email protected]> wrote: > Hi, > > The clear() method in scala.collection.mutable.LinkedHashSet > and scala.collection.mutable.LinkedHashMap does not set lastEntry to null. > In result it holds a reference to an object that was removed from the > collection. > I don't see any reason for that behavior and consider it a bug. > Am I right? > > Jacek > > -- > You received this message because you are subscribed to the Google Groups > "scala-language" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "scala-language" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.