[
https://issues.apache.org/jira/browse/UIMA-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976048#comment-13976048
]
Marshall Schor commented on UIMA-3759:
--------------------------------------
This was traced to test case code not cleaning up after the test - the test
case driver depends on the teardown method to null out refs to artifacts, to
enable the garbage collector to reclaim them. Also found that Yourkit was
reporting many instances of a fairly big object was hanging around, and when
traced to gc roots to see what was holding on, it was traced to an instance of
the CasManager_impl, but *nothing* was holding on to that, except the "JVM".
Yourkit was not helpful (
http://yourkit.com/docs/75/help/performance_problems/memory_leaks/gc_roots.jsp
) . I eventually traced this finally, to the "finalize" method in this class.
This is not a real issue, since a real "major" GC would (most likely) run the
finalize method, and then the JVM would stop holding on to this class instance.
> Investigate possible heap memory issue
> --------------------------------------
>
> Key: UIMA-3759
> URL: https://issues.apache.org/jira/browse/UIMA-3759
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
> Affects Versions: 2.6.0SDK
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: 2.6.0SDK
>
>
> Jenkins builds on some machines with Java 7 latest, are sometimes giving
> out-of-memory failures. Investigate, in case some change caused abnormally
> increased memory use
--
This message was sent by Atlassian JIRA
(v6.2#6252)
