Quantcast

Long hang-times in org.eclipse.equinox.simpleconfigurator

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Long hang-times in org.eclipse.equinox.simpleconfigurator

Brian de Alwis-3
I've noticed in the last couple of weeks that my debug instances sometimes take a loooong time to start, but I'm now seeing it when launching my IDE after updating to Build id: I20170510-2000.

Running with `org.eclipse.osgi/debug/bundleTime=true`, I see:

Finding activator for org.eclipse.osgi_3.12.0.v20170510-2118 [0]
Starting org.eclipse.osgi_3.12.0.v20170510-2118 [0]
End starting org.eclipse.osgi_3.12.0.v20170510-2118 [0] 47
Time to load bundles: 40
Finding activator for org.eclipse.equinox.simpleconfigurator_1.2.0.v20170110-1705 [3]
Starting org.eclipse.equinox.simpleconfigurator_1.2.0.v20170110-1705 [3]
End starting org.eclipse.equinox.simpleconfigurator_1.2.0.v20170110-1705 [3] 49536

and then startup proceeds quickly.  When it happened with debug launches, I found that selectively managing my lists of enabled bundles would bring the time down.

Before I start digging, is there a way to enable debug tracing of some kind in the simpleconfigurator?

Brian.

_______________________________________________
equinox-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Long hang-times inorg.eclipse.equinox.simpleconfigurator

Thomas Watson
I suspect something in your environment is exploding the resolution of the bundles.  Try running with:
 
org.eclipse.osgi/resolver=true
 
That will give you a huge flood of debug output though, but it should show what the resolver is doing while simple configurator is trying to resolve the bundles.  It likely has something to do with uses constraint issues.  You could try only enabling the 'uses' trace option:
 
org.eclipse.osgi/resolver/uses=true

Tom
 
 
 
----- Original message -----
From: Brian de Alwis <[hidden email]>
Sent by: [hidden email]
To: Equinox development mailing list <[hidden email]>
Cc:
Subject: [equinox-dev] Long hang-times in org.eclipse.equinox.simpleconfigurator
Date: Fri, May 12, 2017 9:40 AM
 
I've noticed in the last couple of weeks that my debug instances sometimes take a loooong time to start, but I'm now seeing it when launching my IDE after updating to Build id: I20170510-2000.
 
Running with `org.eclipse.osgi/debug/bundleTime=true`, I see:
 
Finding activator for org.eclipse.osgi_3.12.0.v20170510-2118 [0]
Starting org.eclipse.osgi_3.12.0.v20170510-2118 [0]
End starting org.eclipse.osgi_3.12.0.v20170510-2118 [0] 47
Time to load bundles: 40
Finding activator for org.eclipse.equinox.simpleconfigurator_1.2.0.v20170110-1705 [3]
Starting org.eclipse.equinox.simpleconfigurator_1.2.0.v20170110-1705 [3]
End starting org.eclipse.equinox.simpleconfigurator_1.2.0.v20170110-1705 [3] 49536
 
and then startup proceeds quickly.  When it happened with debug launches, I found that selectively managing my lists of enabled bundles would bring the time down.
 
Before I start digging, is there a way to enable debug tracing of some kind in the simpleconfigurator?
 
Brian.
_______________________________________________
equinox-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev
 


_______________________________________________
equinox-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev
Loading...