Don't you think, that writing Megabytes of logfiles (I have 10 files,
".log", ".bak_0", ..., ".bak_9", each of 1MB and the same timestamp) does
not slow down eclipse drastically?
As far as I can see, Subversion recognises that the resource is closed (by
receiving an exception from setSyncInfo), so far so good. If it is normal
that Eclipse asks for the decoration of a closed resource, Subversion should
simply ignore that call rather than throwing that Exception.
If it is not expected to be asked for the status of a closed resource, I
think I should rather file a bugreport against eclipse.org, right?
Markus
2007/3/16, Mark Phippard <markphip@gmail.com>:
>
> On 3/16/07, Markus Schlegel <schlm3@gmail.com> wrote:
> >
> > My Project config:
> > Projects checked out (initially) to local Disk by using TortoiseSVN or
> > an other SVN Standalone client (but I think this is irrelevant).
> >
> > Import the checked Out Project into Eclipse using the ProjectImport,
> > dont let eclipse copy the project to your workspace.
> > do othis with 2 Projects and close one of them, restart Eclipse.
>
>
> This is how I typically work as well, but I will still factor that in.
> Thanks.
>
>
> BTW: My logfiles are always filled with those exceptions. Now I know why
> > eclipse seems frozen for a minute or two after some operations...
>
>
> I would not be so quick to point the finger at these exceptions as causing
> any performance problems. I doubt they are the source of the freeze.
> Especially if they are coming out of the decorator process as that runs in a
> background thread.
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>
Received on Mon Mar 19 09:20:55 2007