[
http://jira.magnolia.info/browse/MAGNOLIA-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15585#action_15585
]
Grégory Joseph commented on MAGNOLIA-1998:
------------------------------------------
What I can probably already tell you from this, is that the graphs for 3.5
don't show a real flagrant evidence of a leak. At first sight, there are only
minor GC hits. (we can see a major one on page 2 at about 35 minutes, but
that's Magnolia 3.0)
Reducing the Xmx parameter would help the test, by forcing more major GC hits.
After a handful of such hits, the graph will hopefully (rather not ;)) show
evidence of a leak. Until then, seems like your VM just uses what it's been
given.
> Potential memory leak: investigation.
> -------------------------------------
>
> Key: MAGNOLIA-1998
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1998
> Project: Magnolia
> Issue Type: Task
> Reporter: Vivian Steller
> Assignee: Boris Kraft
> Priority: Critical
> Attachments: magnoliaMemLeak_toMag.doc
>
>
> Several users have reported memory issues. We're creating this issue to
> collect information, reports and other evidence. Please attach relevant files
> and leave comments on your experiences. Thanks!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
