Hello,

I've done a little memory profiling with the latest release and I believe I've found the source of a memory leak. I'm using tomcat 5.5.12, java 1.5.0_06
hibernate core 3.2.0.rc2, hibernate annotations 3.2.0.rc1. Using jProbe, I have several classes remaining on the heap after undeployment and many of them have a path to the gc root pointing to: org.hibernate.validator.ClassValidator,
specifically:
private static final ReflectionManager reflectionManager = new JavaXFactory();

there shouldn't be any hibernate classes in the heap after undeployment, right? Can anyone else verify this?

Thanks,
Michael

Hi Christian,

Thanks for your reply, but I would like to humbly disagree and hope you would reconsider. I have tested our app with resin and tomcat (we use resin in production) and I do have anecdotal evidence that the same behavior exists on resin as well. More importantly, I have tested the undeploy memory leak against hibernate 3.0.6 (not recently) and all references to hibernate on the heap were removed on undeploy. I should note this was after we updated to cglib 2.1.3. I really hope this gets considered seriously by the hibernate team, not just dismissed as a tomcat issue, because I'm sure it's importart to many developers.

Thanks
Michael

I have no intention to waste any more time on this. If you want a Hibernate developer to do anything you have to point out exactly where in Hibernate (source) the alleged problem occurs.