Community
Participate
Working Groups
CDT 200405170943 Eclipse 200405140800 I have a large (>300 file) project. When I define a working set that contains a subset of these files and search for enumeration declarations - search will kill eclipse after 7 minutes because it has run out of memory. Please let me know if you want a copy of the project I am using. Note: I was unable to reproduce this problem on Windows
Out of interest, does the same problem occur if you start Eclipse w/512MB of memory (as compared to the 256 which is default)?
I tried 2 consecutive searches (where the IDE was configured with 512MB) and did not get the out-of-memory error, but each search took <7 minutes to complete. Worth noting: I always get the correct # of results in the first 30 seconds, but the remainder of the search just drags on. And when using 256MB, I get the out-of-memory error.
Bog, we'll need to sit down and debug this post-M9Interesting that .
I'm pretty sure this is platform related... Do you get a stack trace?
Unfortunately no.
James - Is this reproducible on a M9 build?
I will move this to 2.0.1. We are targeting 2.0.1 to improve parser performance and memory usage.
Andrew, please validate as to whether or not this has been solved. James, what project were you using to reproduce this exception? Thanks in advance
Using the latest from the 2.0.1 branch with default memory size (256?), I was able to search for * in a workspace containing approx 800 files of generated source. It took approx 3 minutes to find almost 10k matches with no memory problems.
