incubator-odf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dani Prieto (JIRA)" <>
Subject [jira] [Commented] (ODFTOOLKIT-300) Memory Leak in ODF Simple API
Date Fri, 13 Jul 2012 11:48:35 GMT


Dani Prieto commented on ODFTOOLKIT-300:

This issue is solved??? I have this problem with the version odfdom-java-0.8.8-incubating.jar
and simple-odf-0.7-incubating.jar

I execute a similar code and I have seen the heap dump. With Eclipse Memory Analyzer I see
many references to the class  "org.odftoolkit.simple.common.navigation.Selection$SelectionManager"

I am sorry for my englist.
> Memory Leak in ODF Simple API
> -----------------------------
>                 Key: ODFTOOLKIT-300
>                 URL:
>             Project: ODF Toolkit
>          Issue Type: Bug
>          Components: simple api
>    Affects Versions: 0.8.7
>         Environment: odfdom-java-0.8.7.jar; simple-odf-0.6.6.jar
>            Reporter: Mathias Silbermann
>            Assignee: Devin Han
>         Attachments:, TestTextSelection.odt
> There is a memory leak in the ODF Simple API. I tried both, versions 0.6.6 and 0.6.5.
It appears when running code like the examples on cookbook page
> In short, the call TextNavigation.nextSelection() leads to the leak. When you look down
the method's call stack, you will find that items are added to the static variable "repository"
of the static inner class "Selection.SelectionManager". The added items are never removed
from the repository. One indication is that the method Selection.SelectionManager.unregisterItem()
is never called.
> The code works fine if text navigation is done with few documents. But when its run on
a server thousands of times, it will fill the JVMs memory.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message