Community
Participate
Working Groups
Configuration Eclipse SDK Version: 2020-03 (4.15) Build id: I20200130-1800 OS: Linux, v.4.15.0-76-generic, x86_64 / gtk 3.22.30 Java version: 13.0.1 I don't have a quantifiable way of the slowness but when compared to Mac opening of java editor is pretty slow Here are the steps 1. Open a new workspace 2. Create a new java project 3. Create module info file when prompted(Java 9 and above) else create a new class It will take about considerable amount(you can actually see cursor changing to busy for about 4-5 seconds) of time to open java editor. In Mac you don't see any delay the java editor opens quite quickly.
Sravan, can you create some jstacks to see what we are doing?
Eclipse SDK Build id: I20200130-1800 OS: Linux, 5.4.13-201.fc31.x86_64 openjdk version "13.0.1" 2019-10-15 gtk3-3.24.13-1.fc31.x86_64 I'm not seeing a very noticeable delay but I am seeing some delay (~400ms) after NewClassCreationWizard.finishPage() in NewWizardTypePage.createType() . It only takes this long if I choose to avoid creating a module-info file as part of project creation, and then create a source file separately. I guess it could be that creating the module-info handles some of the initial work that would otherwise need to get done at source file creation time. org.eclipse.jdt.ui.wizards.NewTypeWizardPage.createType () 398 ms (100%) 398 ms (100%) -> org.eclipse.jdt.ui.wizards.NewClassWizardPage.createTypeMembers () 197 ms (49.6%) 197 ms (49.6%) -> org.eclipse.jdt.internal.core.PackageFragmentRoot.createPackageFragment () 100 ms (25.3%) 100 ms (25.3%) -> org.eclipse.jdt.ui.wizards.NewTypeWizardPage.createASTForImports () 100 ms (25.2%) 100 ms (25.2%) You could probably try profiling and see if createType() ends up taking seconds for you.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
