[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] 100% CPU in Eclipse - seems due to Subclipse with overlapping projects

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-06-25 02:17:20 CEST

On 6/24/07, Alan Kent <ALAN.J.KENT@saic.com> wrote:
> I am experiencing Eclipse 3.2.2 going to 100% CPU with Subclipse 1.2.2.
> This is under Windows XP. Task Manager shows lots of system time going
> on (say 70% red 30% in the 'performance' tab). Progress monitor often
> reported SVNStatusSubscriber running very slowly. I tried both JavaHL
> and SVNKit - both fail in same way. I have bumped up memory for Eclipse
> (some people were getting 100% CPU due to lack of memory). I don't
> think its memory limit related.
>
> I now think I know the situation in which I create it. I have a Maven
> product with multiple modules. I was using m2eclipse, but it frequently
> plays up (does not work out dependencies correctly) and after spending
> up to an hour a day hitting F5 and restarting Eclipse until it suddenly
> starts working for no apparent reason, I read another way of doing Maven
> with Eclipse was to svn check out all the code under a tree outside the
> Eclipse Workspace and then run mvn eclipse:eclipse to create .project
> files for each module. I can then import all these modules. This means
> I have projects in the workspace, but which refer to the source code off
> in another directory tree. Things seem to work fine, but I lose the
> Subclipse branch/tag/switch etc capability for the whole directory
> tree. So on the web I read a suggestion to import each module as a
> project *AND* import the root directory as a project as well. This is
> possible with the newer versions of Eclipse. That is, the directory
> trees of the source code overlap. I can then use the root project for
> doing svn branch/tag etc commands. I can also use the individual
> projects with their individual classpaths set up by mvn eclipse:eclipse
> - no more need for the m2eclipse plugin.
>
> HOWEVER, it appears that as soon as I create the root project in Eclipse
> that overlaps the existing projects for all the modules, subclipse goes
> insane. I suspect it gets confused by the projects with overlapping
> source trees. As soon as I delete the root project, Eclipse CPU shortly
> after drops to 0% again. Sometimes the delete comes up with an error
> also talking about SVNStatusSubscriber errors (but does delete).
>
> Any help greatly appreciated!

Yes, that is the problem exactly. See this issue:

http://subclipse.tigris.org/issues/show_bug.cgi?id=511

I am not aware of any workarounds other than not use Subclipse or not
use nested projects within Eclipse.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Jun 25 02:17:06 2007

This is an archived mail posted to the Subclipse Users mailing list.