-
Bug
-
Resolution: Done
-
Major
-
4.3.1.Beta2
-
None
-
devex #3 February 2016, devex #116 June 2016
-
20
When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls.
Adding some traces revealed 25 calls to BaseExplorerContentProvider#refreshViewer(Object), which seems way too much for a service with a single pod.
Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services.
Custom/added logs in the console:
Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc Refreshing viewer from sample/jee-sample Refreshing viewer from sample/jee-sample Refreshing viewer from sample/jee-sample Refreshing viewer from sample/jee-sample Refreshing viewer from sample/mongodb Refreshing viewer from sample/mongodb Refreshing viewer from sample/mongodb Refreshing viewer from sample/nodejs-mongodb-example Refreshing viewer from sample/nodejs-mongodb-example Refreshing viewer from sample/nodejs-mongodb-example Refreshing viewer from sample/nodejs-mongodb-example Refreshing viewer from sample/jee-sample Refreshing viewer from sample/jee-sample Refreshing viewer from sample/jee-sample Refreshing viewer from sample/jee-sample Refreshing viewer from sample/nodejs-mongodb-example Refreshing viewer from sample/nodejs-mongodb-example Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
- is related to
-
JBIDE-21449 WatchManager makes multiple callbacks for same event
- Closed
-
JBIDE-21863 WatchManager makes multiple callbacks for same event
- Closed
-
JBIDE-22447 Explorer: Concurrent modification when scaling to a large number of pods
- Closed
-
JBIDE-22643 Explorer: Connection error is shown as child of "Loading...", should replace it
- Closed
-
JBIDE-21668 Fix collection setters in ResourcesUIModel
- Closed
- relates to
-
JBIDE-22603 Sometimes multiple OpenShift watch managers are periodically created and finished
- Closed
-
JBIDE-22447 Explorer: Concurrent modification when scaling to a large number of pods
- Closed
-
JBIDE-22471 Explorer: connection (without stored token) stays "Loading" after I provided the token
- Closed
-
JBIDE-20575 Improve OpenShift Explorer responsiveness
- Closed