incubator-odf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mathias Silbermann (Commented) (JIRA)" <>
Subject [jira] [Commented] (ODFTOOLKIT-300) Memory Leak in ODF Simple API
Date Tue, 07 Feb 2012 07:36:59 GMT


Mathias Silbermann commented on ODFTOOLKIT-300:


the piece of code the lead to the leak is this one:

        TextNavigation match = new TextNavigation(replacementMark, this.templateDocument);
        while (match.hasNext())
            TextSelection selection = (TextSelection) match.nextSelection();

I did a for-loop with 1000 cycles where I loaded the same odt-document in each cycle using:

       this.templateDocument = TextDocument.loadDocument(this.templateFilePath);

After opening a document, I replaced many words using the first piece of code for each word
to be replaced.
In the end of each cycle, I saved the document using;

You can use jConsole to see the growing memory consumption of the jvm running the 1000-cycle
> 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
> 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