Bug solved in the CVS and expected to be in 1.6rc2 Kees fixed it while i was on the phone it seems, i added a second fix but i think both fixed make sense to keep. This is a important fix so please if you are running a large(r) site please test this fix for us. I would also like several commitors to take a look at the 2 fixed classes (MultiLevelCacheHandler.java and BasicCloud.java) and do some codereview on our fixes.
Greetings and thx for the clear bugreport and test program, Daniel and Keesj. >-----Oorspronkelijk bericht----- >Van: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED]]Namens Daniel Ockeloen >Verzonden: dinsdag 26 november 2002 22:45 >Aan: [EMAIL PROTECTED] >Onderwerp: RE: memory leak in multilevel cache > > > > >>-----Oorspronkelijk bericht----- >>Van: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED]]Namens Joost Diepenmaat >>Verzonden: dinsdag 26 november 2002 13:15 >>Aan: [EMAIL PROTECTED] >>Onderwerp: memory leak in multilevel cache >> >> >>Hello people, >> >>I've been doing some tests on the 1.5.1 version regarding the extreme >>amount of memory that cloud.getList() seems to allocate. It turns out >>that if I issue a multilevel query that returns 10 Nodes, and repeat >>this 10,000 times, the amount of memory the JVM needs grows with about >>10 Mb and doesn't go down again, crashing the JVM after about 60,000 >>queries depending on configuration. >> >>This only happens when the multilevel cache is on, otherwise memory >>usage stays even. Which turns out not to be much slower anyways - at >>least for very simple queries. >> >>Attached is a JSP page that demonstrates the problem. >> >>Does anyone have a solution / patch for this problem? We do need the >>multi-level queries, so our only option now is to disable the >>multi-level cache. >> >>Greets, >> >>Joost Diepenmaat >>Framfab Nederland BV >> > > >Ill take a look at it tonight, if it doesn't give problems with multilevel >off its clearly a problem inside that code... > >Daniel. > > >
