You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Damian Steer (JIRA)" <ji...@apache.org> on 2011/08/16 00:55:27 UTC
[jira] [Created] (JENA-101) Memory leak in Fuseki
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
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
[jira] [Closed] (JENA-101) Memory leak in Fuseki
Posted by "Damian Steer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Damian Steer closed JENA-101.
-----------------------------
> 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
> 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
[jira] [Updated] (JENA-101) Memory leak in Fuseki
Posted by "Damian Steer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Damian Steer updated JENA-101:
------------------------------
Priority: Major (was: Minor)
Bumped to 'major', affects all stores.
> 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
> 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
[jira] [Issue Comment Edited] (JENA-101) Memory leak in Fuseki
Posted by "Damian Steer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085638#comment-13085638 ]
Damian Steer edited comment on JENA-101 at 8/16/11 11:20 AM:
-------------------------------------------------------------
Fixed in #1158152
was (Author: shellac):
Fixed in r1158152
> 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
> 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
[jira] [Issue Comment Edited] (JENA-101) Memory leak in Fuseki
Posted by "Damian Steer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085638#comment-13085638 ]
Damian Steer edited comment on JENA-101 at 8/16/11 11:20 AM:
-------------------------------------------------------------
Fixed in r1158152
was (Author: shellac):
Fixed in #1158152
> 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
> 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
[jira] [Commented] (JENA-101) Memory leak in Fuseki
Posted by "Damian Steer (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (JENA-101) Memory leak in Fuseki
Posted by "Damian Steer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Damian Steer resolved JENA-101.
-------------------------------
Resolution: Fixed
Fixed in r1158152
> 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
> 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