You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2007/07/13 15:25:04 UTC
[jira] Created: (JCR-1032) Clean caches in node type registry on
session logout
Clean caches in node type registry on session logout
----------------------------------------------------
Key: JCR-1032
URL: https://issues.apache.org/jira/browse/JCR-1032
Project: Jackrabbit
Issue Type: Improvement
Components: SPI
Reporter: Marcel Reutegger
Priority: Minor
When running the JCR tests the memory consumption increases steadily. At the end of the test run it consumes about 300 Mb on my machine. There's not really a memory leak in jcr2spi, because the JUnit tests keep references to Session and Node instances until the end of the test run, but it would be nice if those instances were a bit more lightweight.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1032) Clean caches in node type registry on
session logout
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved JCR-1032.
-----------------------------------
Resolution: Fixed
Fixed in revision: 555986
> Clean caches in node type registry on session logout
> ----------------------------------------------------
>
> Key: JCR-1032
> URL: https://issues.apache.org/jira/browse/JCR-1032
> Project: Jackrabbit
> Issue Type: Improvement
> Components: SPI
> Reporter: Marcel Reutegger
> Priority: Minor
>
> When running the JCR tests the memory consumption increases steadily. At the end of the test run it consumes about 300 Mb on my machine. There's not really a memory leak in jcr2spi, because the JUnit tests keep references to Session and Node instances until the end of the test run, but it would be nice if those instances were a bit more lightweight.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1032) Clean caches in node type registry on
session logout
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512478 ]
Marcel Reutegger commented on JCR-1032:
---------------------------------------
Tests now run successfully with the default heap size of 64 mb.
> Clean caches in node type registry on session logout
> ----------------------------------------------------
>
> Key: JCR-1032
> URL: https://issues.apache.org/jira/browse/JCR-1032
> Project: Jackrabbit
> Issue Type: Improvement
> Components: SPI
> Reporter: Marcel Reutegger
> Priority: Minor
>
> When running the JCR tests the memory consumption increases steadily. At the end of the test run it consumes about 300 Mb on my machine. There's not really a memory leak in jcr2spi, because the JUnit tests keep references to Session and Node instances until the end of the test run, but it would be nice if those instances were a bit more lightweight.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1032) Clean caches in node type registry on
session logout
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-1032:
-------------------------------
Fix Version/s: 1.4
> Clean caches in node type registry on session logout
> ----------------------------------------------------
>
> Key: JCR-1032
> URL: https://issues.apache.org/jira/browse/JCR-1032
> Project: Jackrabbit
> Issue Type: Improvement
> Components: SPI
> Reporter: Marcel Reutegger
> Priority: Minor
> Fix For: 1.4
>
>
> When running the JCR tests the memory consumption increases steadily. At the end of the test run it consumes about 300 Mb on my machine. There's not really a memory leak in jcr2spi, because the JUnit tests keep references to Session and Node instances until the end of the test run, but it would be nice if those instances were a bit more lightweight.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.