Community
Participate
Working Groups
Please see bug 290813 for background. I am splitting that bug into two since it covers two different issues, and the relevant one to track here is this: > From further use, I've found that when I make a change (e.g. add a temp > fix, or add the core tools) p2 usually doesn't pick it up on the first > start (!), takes [...] time to start the second time, and then > randomly takes this long again on the third or fourth start. In other words, p2 does not notice changes on disk on every start. Once it has reconciled these changes, it often reconciles unnecessarily again within a few restarts.
If you are running on Eclipse 3.5 or greater, there are some tracing options that should give us more detail about what is going on here: org.eclipse.equinox.p2.core/debug=true org.eclipse.equinox.p2.core/reconciler=true This will print details on what p2 thinks has changed, which may help us understand what's going on in your case. I'm going to run with this turned on as well to see if I can spot this happening. I suspect our reconcile is fast enough on small installs that we wouldn't notice if this was happening.
Created attachment 150873 [details] Reconciler trace with no changes on disk Since the original bug report I haven't touched the install that I reported this on. However, for full disclosure I did use IM to install an earlier version of the product (on Eclipse 3.4.2), so my shared plugin folder has amassed both sets of plugins. Here's what I did to test: 1. Added the trace options above. 2. Launched product once to confirm tracing worked. The workspace selection dialog appeared without delay. 3. Touched an Eclipse core tools plugin (in the product folder, not the shared plugins folder) so that the reconciler would think something has changed. 4. Launched the product. It took 1m55s CPU time before the workspace selection dialog appeared, and lots of trace. 5. Shutdown product, and launched again. This time it took 1m30s even though nothing had changed on disk. Trace attached here. 6. Launched a third time, this time no delay. In this test it correctly picked up the changes on first launch, but reconciled again unnecessarily on second launch. The first 45s in the trace is spent in org.eclipse.equinox.p2.directorywatcher before the new tracing options kick in, so not sure if these tracing options will help.
This issue looks like a duplicate of 313905, althought I am not 100% sure.
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. -- The automated Eclipse Genie.
This bug was marked as stalebug a while ago. Marking as worksforme. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
