Bug 218673 [DataBinding] SWTUtil should use timerExec(0,...) rather than asyncExec
In the event that you have a lot of cross-realm bindings, the current implementation of DisplayRealm generates a lot of flicker due to excess asyncExecs. It should be using SWTUtil.greedyExec instead. (Note: if you make this change, you may want to remove the display filter from WorkQueue. There are certain methods that do not like being called from an event filter, so running arbitrary asyncExecs during a filter may not always be safe.)
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/swt/SWTUtil.java
if (result < 0) result = 0;
        if (result > 255) result = 255;
        return result;
    }
    
	/**
	 * Logs an exception as though it was thrown by a SafeRunnable being run
	 * with the default ISafeRunnableRunner. Will not open modal dialogs or spin
	 * the event loop.
	 * 
	 * @param t
	 *            throwable to log
	 * @deprecated
	 * @noreference This method is not intended to be referenced by clients. It
	 *              remains here for API backwards compatibility.
	 */
	public static void logException(final Exception t) {
		SafeRunnable.run(new SafeRunnable() {
			public void run() throws Exception {
				throw t;
			}
			public void handleException(Throwable e) {
				
				
				
			}
		});
	}
}