[ https://issues.jboss.org/browse/JBIDE-15887?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15887 at 11/7/13 6:01 AM: ------------------------------------------------------------------- I have no clue what is causing this. I tried with a fresh Eclipse IDE and it didnt help. Connecting jvisualvm did not unveils major activity of org.eclipse.core.internal.databinding.beans.BeanPropertyHelper#readProperty right after native GTK (most likely key events) !visual-vm.png! I noticed that when you change the name of the application you trigger 3 MultiValidators: - ApplicationConfigurationWizardPage#NewApplicationNameValidator - ProjectAndServerAdapterSettingsWizardPage#UseExistingOpenProjectValidator - GitCloningSettingsWizardPage#RepoPathValidationStatusProvider This is required since the application name is the name of the new workspace project that the application will get imported into (thus needs to be validated aka made sure no such proj exists). And the application name is also used for the folder that the application is cloned into (and thus needs to get validated, too). The lagging improves a lot as soon as I comment some validators (just the body, not the creation). was (Author: adietish): I have no clue what is causing this. I tried with a fresh Eclipse IDE and it didnt help. Connecting jvisualvm did not unveils major activity of org.eclipse.core.internal.databinding.beans.BeanPropertyHelper#readProperty right after native GTK (most likely key events) !visual-vm.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira