Bug 210525 - shutdown takes several minutes
Summary: shutdown takes several minutes
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2007-11-21 07:16 EST by Martin Aeschlimann CLA
Modified: 2019-11-06 04:46 EST (History)
2 users (show)

See Also:


Attachments
stacktrace with timing information (101.68 KB, text/html)
2007-11-21 07:19 EST, Martin Aeschlimann CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Aeschlimann CLA 2007-11-21 07:16:56 EST
3.3

The shutdown of my development workspace takes several minutes, depending on how long the Eclipse session has lasted.
The workspace is quite old and contains lots of projects.

The profile trace taken by yourkit shows that 
org.eclipse.team.internal.core.subscribers.SubscriberResourceCollector.resourceChanged(
takes almost half of the time.

It's not clear if does anything but looking at the delta.

It would also be interesting to see how big this delta is. I normally close my workspace with all resources saved. I don't know what kind of resource change could be reported here.

Is there debug option to log the delta?
Comment 1 Martin Aeschlimann CLA 2007-11-21 07:19:43 EST
Created attachment 83422 [details]
stacktrace with timing information

Full yourkit dump is available on request.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:35:42 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 3 Lars Vogel CLA 2019-11-06 04:46:08 EST
Please reopen if this still in the case for 4.13.