Friendly Jira Robot created ERT-220: --------------------------------------- Summary: [performance] Property tab contributors should avoid processing in UI thread [EBZ#494660] Key: ERT-220 URL: https://issues.jboss.org/browse/ERT-220 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot This related to Bug 494585, and generalizes to all classes that extend BasePropertySection. The current logic for property sections is to query the necessary data using the connection (sometimes this is cached so it's fast, sometimes it's not) in a separate job. The UI thread waits at most 2 seconds for the data, or sends no data back to the property view. Even a 2 second wait can be a lot and makes the UI seem unresponsive, so it's best to convert all of these to work asynchronously. The bug I've mentioned does exactly this. We immediately set the tree view input data as null and kick off a separate job that will asynchronously update the UI if fetching the data succeeded. I don't mind holding off on this for after 5.0.0 as a few of these property contributors deal with cached data, and even for the data that is fetched directly from the daemon, the delay is negligible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)