JCarder 2.0.0 analyzer runs "forver" and/or throws OOME

23 views
Skip to first unread message

Andrey Aleshnikov

unread,
Oct 15, 2013, 11:41:29 AM10/15/13
to jca...@googlegroups.com
Guys,


We have an app with heavy concurrency. The problem is JCarder analyzer eats up all heap memory and not making any noticeable progress due to GC (see screenshots below).
E.g. we have jcarder_contexts.db of 12.41 MB, jcarder_events.db of 2.15 GB and run analyzer on 7u40 amd64 with
java.exe -server -XX:+AggressiveOpts -Xms8G -Xmx14G -jar path/to/jcarder.jar  -outputmode cycles -printdetails -d path/to/db/dir
and it would throw OutOfMemoryError: GC overhead limit exceeded after tens of minutes. Same result for -outputmode mtcycles. Some time ago we tried to use -XX:-UseGCOverheadLimit, it just made analyzer run for a couple of weeks util we killed it.
Is there a chance to address this problem? Are there any workarounds available?

 


-Thanks
jcarder.tdump
jcarder.console_log.txt
Reply all
Reply to author
Forward
0 new messages