Memory leak with simple example code ------------------------------------ Key: JBPM-827 URL: http://jira.jboss.com/jira/browse/JBPM-827 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.3, jBPM 3.1.2 Environment: java 1.4.2 Reporter: Johan Parent Assigned To: Tom Baeyens The Websale example wrapped in a simple for-loop in standalone app. reveals what resembles a memory leak. Performance degrades severely as the JVM starts to do some expensive gc after 4000 iterations. At that time the JVM consume more than 274Mb of ram (JVM not started with special -X options!) Problem occurs with HSQLDB as well as Sybase db. The code to reproduce this problem has been posted here http://www.jboss.com/index.html?module=bb&op=viewtopic&t=99440 Iter. ms (per iter.) -------------------------- 3993 291 3994 280 3995 281 3996 300 3997 270 3998 301 3999 290 4000 281 4001 2093 4002 270 4003 310 4004 271 4005 280 4006 291 4007 300 4008 280 4009 2183 4010 281 4011 290 4012 281 4013 270 4014 311 4015 280 4016 280 4017 2083 4018 301 4019 270 4020 290 4021 281 4022 300 4023 281 4024 280 4025 2113 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira