Community
Participate
Working Groups
i always get the error of 'out of memory' when i use ctrl+shift+g to get the references of function 'init()' of my class AbstractView. my class definition public abstract class AbstractView extends JPanel implements ... when i put ctrl+shift+g on funtion 'init()', the error occurs. if i put ctrl+g on funtion 'init()', then all the classes which has a function 'init()' in my classpath are find out. but if i change the function name to another one such as 'init2()', i easily get the right result. so i know that why ctrl+shift+g on init() cause out of memory error. The find mechanisum is wrong when the funtion name is init() here. please find out why and fix it :)
This is for 3.0.2, right? Make sure to start the vm with enough memory, e.g. at least 256MB (option -Xmx256M). Moving to jdt.core.
Most of search requests are currently working with -Xmx256M in a full-source workspace (ie. all eclipse 3.0 plugins loaded with sources). Of course this is highly dependent of number of plugins you have loaded in your workspace and number of java or class files they have in (included internal and external jars files). We've made some improvement in 3.1 but still have some troubles when search returns a heavy large number of matches. This is something we'll surely plan to work early 3.2 (see bug 99114 & bug 99938 - currently set as LATER while waiting for 3.1 delivery, but prioriterized P2). Unfortunately, as most of search requests work with standard VM heap size (256M is a reasonable value), we will not plan to fix this issue in next rollup as it would be too risky for maintenance builds. If your configuration is really specific and you already has set VM heap size to 256M, then perhaps try an higher value as 512 or 1024 if you box can allow it and let me know if this fix your problem, thx
Reopen when providing requested feedback, thanks
Thanks for the explanations. I added the arguments of '-vmargs -Xmx1024M' , and I got the right eclipse.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
