[Bug swing/26368] New: Possible memory leak in GapContent

[roman at kennke dot org]

In GapContent we store all created Position instances in an ArrayList. However,
we never do remove any Position instances, even when they are not used anymore.
With large documents and lots of editing this will blow up significantly (not
an issue yet, since text components are not yet working very reliably, but...).
I have not completely made up my mind about what will be the best solution. We
will likely need some WeakReferences in the ArrayList, but then, these must be
cleared up regulary and reliably etc.


-- 
           Summary: Possible memory leak in GapContent
           Product: classpath
           Version: 0.21
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: swing
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: roman at kennke dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26368