- This topic has 39 replies, 9 voices, and was last updated 20 years, 6 months ago by
Riyad Kalla.
-
AuthorPosts
-
dboyditsMemberAfter installing 3.8.0 I can no longer search. Any kind of search I perform ends up in some kind of endless loop, and eventually runs the JVM out of memory forcing me to kill the process from the windows task manager.
Any search I do seems to work as the results I expect show up in the search pane and the progress indicator in the status bar says “Java Search: (100%)” but the search just continues to run. In the Search progress dialog there is a “JSP Search indexing workspace” task running. I try and cancel it, but it won’t quit. It just runs the JVM out of memory forcing me to kill the app.
Everything was working fine before I installed 3.8.0. I was running beta2. When I installed 3.8.0, I had eclipse shutdown and I renamed the old MyEclipse directory to MyEclipse-old before installing (i.e. I didn’t install over the beta2 version).
Is there any way I can disable this JSP Indexing? I would very much like to continue to use the search and MyEclipse.
Thanks
Riyad KallaMemberUnfortunately this is a known problem with the indexer from the JDT team, it leaks memory like a sieve… I am checking with the team to see if we can work around it in any way.
Diego Ernesto Malpica ChauvetParticipantI have the same problem =((( it makes java searchs an some refactors unusable. This problems does not come out in 3.8.0 beta2, I will try with 3.8.1
Riyad KallaMemberWe have disabled the indexer temporarily in the later 3.8.1 + Quickfix releases, so you guys shouldn’t run into this problem until we get it fixed.
Diego Ernesto Malpica ChauvetParticipantStill doen’t wok with 3.8.1 =((
Riyad KallaMemberDid you apply the quickfixes? (be careful to follow the instructions closely)
https://www.genuitec.com/forums/topic/third-quickfix-for-myeclipse-3-8-1-is-available/#post-213816
jaeParticipantthis isn’t disabled in the quick fix releases.
my build id is reported as the following: 200408201200-3.8.1+QF20040825
Riyad KallaMemberThe indexer *was* disabled for 3.8.1, it should not be causing the OOM exceptions anymore and you should still be able to search. I just searched 4 web module projects and 2 Java projects in “*” files for the string “class” and it worked fine.
Have you guys tried shutting down Eclipse, deleting your <eclipse dir>\configuration directory and then starting Eclipse and re-adding MyEclipse via the Help > Soft Updates > Manage Configs > (right click) > “Add…” and adding the MyEclipse extension back again and restarting?
jaeParticipantmy applogies, i am not having problems w/ searching, i am having issues trying to refactor a method name.
as soon as eclipse display “creating workspace modification” in the progress box after clicking ok to refactor the method name, it just hangs. once i cancel the operation and look at the progress menu, it is stuck running the jsp indexer, and the only way i can regain control of eclipse to do anything useful is to restart it.
Riyad KallaMemberOhh I see, are you refactoring a bean that is used in JSP pages or is it just any class from a Web Module Project? I will try and reprodce this locally..
jaeParticipanti am not 100% sure (new job, still don’t know all ins and outs of the code base yet).
the class is in a project that is referenced by a Web Module project – no JSPs access the class directly, but they do access other classes that then access the class i am trying to refactor.
ie: JSP -> Delegate Class -> Class Trying to be Refactored
Riyad KallaMemberHmm I see, ok I’ll try a few test cases locally (normal project, web project, then a dependecy between the two).
Thanks!
jaeParticipanttrying this on my own yeilds the search indexer running reguardless of the project type and whether or not it has any dependencies to a project that contains jsps.
Riyad KallaMemberok thank you for the details
jaeParticipantany updates on this? it’s critical eclipse functionality that i am unable to use.
-
AuthorPosts