The little test probably didn't demo it in an obvious way. But I don't think it is just a fluctuation of memory usage -- a couple of hours on my own project, all my 2G virtual memory are consumed. Not something in beta 3. Garbage collection doesn't help either.
I won't say what I have is concrete evidence of a mem leak of the IDE, just some observed difference in behavior. I wanted to share it and see if someone else has a similar experience. Is anyone using the RC1 IDE at all? I'll give M6 a shot. Thanks, Yuesong --- Michael Neale <[EMAIL PROTECTED]> wrote: > I think since the beta the builder was changed to > build whenever the > resources changed, so that if you change a java > object, and a rule depends > on it, it will show up appropriately. You might be > seeing the effect on > that. As to if its a leak, well keep doing that, and > then press the garbage > collect button and see if it reclaims it. Normal > operation is for mem to go > up and down like that. > > The task manager in windows is not always > informative, other then over a > long period of time. As the heap grows, the JVM can > request more from the > OS, even if it doesn't use it the task manager will > show it. Apparently in > java 6 or 7 that is all changing, but for now, have > a look at what the > little eclipse meter (down the bottom in M5) says. > > Of course, a leak is always possible, the IDE has to > do all sorts of stuff > to parse/build the rules, sniff out DSLs etc.. (even > the colours) but as you > say, its recent behaviour, so I am thinking the main > thing that changed is > the builder. > > Please let us know what you find. > > > Michael. > > (ps just trying out M6, still some issues - 3.2 > final is due in June, gosh I > hope it comes quickly !). > > > > On 4/7/06, Yuesong Wang <[EMAIL PROTECTED]> > wrote: > > > > I installed the RC1 IDE this morning and started > using > > it. There appeared to be some kind of memory leak > that > > was not in the beta 3 version. The mem usage grew > > every time the project was built. The more rules > the > > bigger the jump. Have to restart Eclipse to clean > it > > up. > > > > Here's a little test that I run to try to > reproduce > > the issue: > > > > - Install a fresh copy of Eclipse 3.2M5a, > > and the RC1 IDE > > - Use the wizard to create a new Drools project > > - Make sure auto build on > > - Ctrl_c to copy the Sample drl file > > - Keep hitting Ctrl_p to add new copies (each > > copy causes a rebuild) > > > > Have task manager open at the same time and watch > the > > mem usage go up. > > > > To compare, do the same thing with beta 3 IDE, the > mem > > usage increase is far less obvious, and garbage > > collection can reclaim it. > > > > Did anyone else notice this? > > > > Thanks, > > > > Yuesong > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam > protection around > > http://mail.yahoo.com > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
