[
https://issues.apache.org/jira/browse/JENA-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085596#comment-13085596
]
Damian Steer commented on JENA-101:
-----------------------------------
Issue confirmed with persistent store. Upload is parsed to an in-memory graph
first, so store is irrelevant.
Will look for other examples of unclosed sinks.
> Memory leak in Fuseki
> ---------------------
>
> Key: JENA-101
> URL: https://issues.apache.org/jira/browse/JENA-101
> Project: Jena
> Issue Type: Bug
> Components: Fuseki
> Reporter: Damian Steer
> Priority: Minor
> Labels: fuseki, memory_leak
>
> Steps to reproduce:
> 1. Start fuseki in memory mode with updates enabled.
> 2. Repeatedly PUT an N-Triple or turtle file to the same graph.
> 3. Attach VisualVM.
> 4. Memory use slowly grows and is not all collected.
> Explanation:
> The parser uses the sink SinkTriplesToGraph, which registers itself with the
> global RIOT event manager. The sink is never closed by fuseki, and so is
> never unregistered, which means the sink remains reachable. The sink also has
> a reference to the graph, so each added graph remains forever.
> Closing the sink seems to fix the issue. Not clear if this is especially a
> memory mode issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
