Hi,
Since 1.3.12 I have noticed a significant increase (x3 at least) in the amount of actual physical memory being used by Eclipse + PyDev. I noticed there is some new caching taking place now, but the release notes said that should have zero memory impact. Anyway, pydev is almost unusable on my laptop (with limited memory) now whereas it was perfectly fine before. This is on OS X 10.5.1 with Java 5. Any idea what is up? Is it possible to turn the extra caching off?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's strange... the actual caching will only start caching when a completion request is issued and should garbage collect all that memory when it's finished (and it would actually go on and create that memory anyways... the difference is that it would create it and garbage collect it right away, and now it waits until the end of the completion request).
Still, maybe I did something wrong there and introduced some memory leak, but that needs more investigation before confirming it... Can you please report it as a bug... please add: Are you with the same libraries? How much memory is it taking? How much was it taking with the previous version?
Cheers,
Fabio
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Since 1.3.12 I have noticed a significant increase (x3 at least) in the amount of actual physical memory being used by Eclipse + PyDev. I noticed there is some new caching taking place now, but the release notes said that should have zero memory impact. Anyway, pydev is almost unusable on my laptop (with limited memory) now whereas it was perfectly fine before. This is on OS X 10.5.1 with Java 5. Any idea what is up? Is it possible to turn the extra caching off?
That's strange... the actual caching will only start caching when a completion request is issued and should garbage collect all that memory when it's finished (and it would actually go on and create that memory anyways... the difference is that it would create it and garbage collect it right away, and now it waits until the end of the completion request).
Still, maybe I did something wrong there and introduced some memory leak, but that needs more investigation before confirming it... Can you please report it as a bug... please add: Are you with the same libraries? How much memory is it taking? How much was it taking with the previous version?
Cheers,
Fabio