August 23, 2019 at 6:15 pm #621554
As of late, MyEclipse takes 5-10 minutes to go from the splash screen to the IDE opened on the workspace. The process consumes 50-75% of the CPU and power. I don’t know what I could have done of late that would cause this to occur. CodeMix is disabled.
I’ve run jstack against the process’ PID and have attached the results here.
Thanks for your suggestions. I’ll be out for around a week and will check in later.
Attachments:You must be logged in to view attached files.August 26, 2019 at 5:43 am #621664
Same here.. is a pain now. Using Windows 10 and JDK8August 26, 2019 at 1:08 pm #621736
Sorry to hear you are running into this; 5-10 minutes to start is definitely not expected.
First, just to get something obvious out of the way, If you haven’t read our post on Windows Defender causing slow starts, do read and see if making the changes suggested helps: https://www.genuitec.com/stop-slow-eclipse-myeclipse-startups/
Todd – thanks for taking the trouble to send us the dump, unfortunately nothing obvious in there.
afxgroup – I know we discussed this before, where you said the latest version of MyEclipse made it fast again. I’m guessing you are now using 2019.4 and this is no longer true? Any changes since our previous discussion?
1) If you shut down MyEclipse and start again in the same session, does it still take the same amount of time?
2) Can you both try switching to a blank workspace to see if the workspace and/or the set of projects you’re working with is causing the slowdown?
3) Any additional plugins added to the installation?August 29, 2019 at 5:14 am #622142
Just checking in – were you able to try any of the steps I mentioned above? Would be happy to look deeper into this as required.September 3, 2019 at 9:59 am #622911
Hi Brian –
Some feedback on my end. After being away for a week, I restarted my machine and saw a quick startup for MyEclipse – < 1 min. I then ran a CodeMix update (I have CodeMix disabled) and I’m back to seeing slow startups. Not as slow as before, but in the range of 3 minutes.
I tried opening MyEclipse on an empty workspace, and see the same startup time.
Installation details below:
*** Date: Tuesday, September 3, 2019 10:57:35 AM EDT *** System properties: OS=Windows10 OS version=10.0.0 OS arch=amd64 Profile arch=x86_64 Window system=win32 Java version=1.8.0_191 Workspace=file:/C:/eclipseWorkspaces/EQA/ VM Args=-Xms256m -Xmx1024m -XX:+UseG1GC -XX:+UseStringDeduplication -Dosgi.requiredJavaVersion=1.8 -Dosgi.nls.warnings=ignore -Davailable.updates.autoexpand=true -Djava.class.path=C:\MyEclipseCI\plugins\org.eclipse.equinox.launcher_1.5.200.v20180922-1751.jar *** Subscription information Product Id: E3MP (MyEclipse Professional Subscription) License version: 3.0 Full Maintenance Included Subscription expiration date (YYYYMMDD): 20200415 Number of users: 1 *** Eclipse details: MyEclipse Enterprise Workbench Version: CI 2019.4.0 Build id: 16.0.0-20190403 com.genuitec.myeclipse.database - 15.0.1.me201904021204 com.genuitec.myeclipse.desktop - 14.0.0.me201904021204 com.genuitec.myeclipse.enterprise.workbench - 14.0.0.me201904021204 com.genuitec.myeclipse.icefaces.feature - 14.0.0.me201904021204 com.genuitec.myeclipse.imageeditor - 14.0.0.me201904021204 com.genuitec.myeclipse.jsf - 14.0.0.me201904021204 com.genuitec.myeclipse.maven - 14.0.0.me201904021204 com.genuitec.myeclipse.persistence - 14.0.0.me201904021204 com.genuitec.myeclipse.reports - 14.0.0.me201904021204 com.genuitec.myeclipse.struts - 14.0.0.me201904021204 com.genuitec.myeclipse.uml2 - 14.0.0.me201904021204 com.genuitec.myeclipse.visualvm - 14.0.0.me201904021204 com.genuitec.myeclipse.ws - 14.0.0.me201904021204 com.skyway.myeclipseforspring.feature - 15.0.1.me201904021204 org.eclipse.birt - 4.8.0.me201904021204 org.eclipse.datatools.connectivity.feature - 1.14.101.me201904021204 org.eclipse.datatools.enablement.feature - 1.14.101.me201904021204 org.eclipse.datatools.modelbase.feature - 188.8.131.52811012051 org.eclipse.datatools.sqldevtools.feature - 1.14.101.me201904021204 org.eclipse.emf - 2.16.0.v20181206-1055 org.eclipse.gef - 184.108.40.206606061308 org.eclipse.graphiti.feature - 0.15.0.201806050830 org.eclipse.jpt.jpa.feature - 3.5.101.me201904021204 org.eclipse.jpt.jpadiagrameditor.feature - 1.2.300.me201904021204 org.eclipse.jst.common.fproj.enablement.jdt - 3.11.0.me201904021204 org.eclipse.jst.enterprise_ui.feature - 3.9.2.me201904021204 org.eclipse.jst.server_adapters.ext.feature - 3.3.602.me201904021204 org.eclipse.jst.server_adapters.feature - 3.2.500.me201904021204 org.eclipse.jst.server_ui.feature - 3.4.300.me201904021204 org.eclipse.jst.ws.axis2tools.feature - 1.1.301.me201904021204 org.eclipse.m2e.feature - 1.10.0.me201904021204 org.eclipse.sapphire.platform - 220.127.116.11712191343 org.eclipse.wst.common.fproj - 3.7.2.me201904021204 org.eclipse.wst.server_adapters.feature - 3.2.700.me201904021204 org.eclipse.xsd - 2.16.0.v20181127-0852 org.springframework.ide.eclipse.feature - 3.9.7.me201904021204 angularjs-eclipse-feature - 1.2.0.me201904021204 angularjs-eclipse-jsp-feature - 1.2.0.me201904021204 angularjs-eclipse-php-feature - 1.2.0.me201904021204 com.eclipsesource.j2v8.feature - 18.104.22.168704121300 com.github.eclipsecolortheme.feature - 1.0.0.me201904021204 com.ianbrandt.tools.m2e.mdp.feature - 0.0.4.201409291703 com.seastreet.genesys.designer.feature - 22.214.171.124906032036 fr.obeo.acceleo.bridge.feature - 2.6.0.me201904021204 io.emmet.eclipse - 14.0.0.me201904021204 jdt-codemining-feature - 126.96.36.199808021134 net.jeeeyul.pdetools.feature - 1.2.9.me201904021204 net.jeeeyul.swtend.feature - 2.2.5.me201904021204 org.chromium.debug - 0.3.9.201903271144 org.chromium.sdk - 0.3.9.201903271144 org.chromium.sdk.wipbackends - 0.1.11.201903271144 org.codehaus.groovy.compilerless.feature - 3.5.0.v201909030034-e1812 org.codehaus.groovy.eclipse.feature - 3.5.0.v201909030034-e1812 org.codehaus.groovy.headless.feature - 3.5.0.v201909030034-e1812 org.codehaus.groovy.jdt.patch - 3.5.0.v201909030034-e1812 org.codehaus.groovy24.feature - 3.5.0.v201909030034-e1812 org.codehaus.groovy25.feature - 3.5.0.v201909030034-e1812 org.dadacoalition.yedit.feature - 188.8.131.52903271150 org.eclipse.buildship - 3.0.0.v20181106-1441-m org.eclipse.cvs - 1.4.700.v20181206-0815 org.eclipse.draw2d - 184.108.40.206606061308 org.eclipse.e4.rcp - 1.6.300.v20181204-1801 org.eclipse.ecf.core.feature - 1.5.3.v20181012-2020 org.eclipse.ecf.core.ssl.feature - 1.1.100.v20180301-0201 org.eclipse.ecf.filetransfer.feature - 3.14.4.v20181013-2146 org.eclipse.ecf.filetransfer.httpclient4.feature - 3.14.4.v20181013-2146 org.eclipse.ecf.filetransfer.httpclient4.ssl.feature - 1.1.100.v20180301-0132 org.eclipse.ecf.filetransfer.ssl.feature - 1.1.100.v20180301-0132 org.eclipse.egit - 220.127.116.11812061821-r org.eclipse.epp.mpc - 1.7.3.v20181205-1546 org.eclipse.equinox.p2.core.feature - 1.6.0.v20181123-1405 org.eclipse.equinox.p2.discovery.feature - 1.2.100.v20180822-1357 org.eclipse.equinox.p2.extras.feature - 1.4.200.v20181123-1405 org.eclipse.equinox.p2.rcp.feature - 1.4.200.v20181123-1405 org.eclipse.equinox.p2.user.ui - 2.4.200.v20181123-1405 org.eclipse.help - 2.2.400.v20181206-0815 org.eclipse.jdt - 3.16.0.v20181206-1038 org.eclipse.jet - 1.1.1.v201101271243-5319sC7HCAGERASDK3924 org.eclipse.jet.uml2 - 1.1.0.v201006011447-2-07w311A1A152813 org.eclipse.jgit - 18.104.22.168812061821-r org.eclipse.jgit.ssh.apache - 22.214.171.124812061821-r org.eclipse.jsf.feature - 3.10.0.me201904021204 org.eclipse.mylyn.commons - 3.24.2.v20180904-2231 org.eclipse.mylyn.commons.identity - 1.16.0.v20180904-2231 org.eclipse.mylyn.commons.notifications - 1.16.0.v20180904-2231 org.eclipse.mylyn.commons.repositories - 1.16.0.v20180904-2231 org.eclipse.mylyn.context_feature - 3.24.2.v20180905-0014 org.eclipse.mylyn.discovery - 3.24.2.v20180904-2231 org.eclipse.mylyn.ide_feature - 3.24.2.v20180905-0014 org.eclipse.mylyn.java_feature - 3.24.2.v20180905-0014 org.eclipse.mylyn.monitor - 3.24.2.v20180904-2231 org.eclipse.mylyn.tasks.ide - 3.24.2.v20180905-0003 org.eclipse.mylyn.team_feature - 3.24.2.v20180905-0014 org.eclipse.mylyn.wikitext.editors_feature - 126.96.36.199908301739 org.eclipse.mylyn.wikitext.extras_feature - 188.8.131.52908301739 org.eclipse.mylyn.wikitext_feature - 184.108.40.206908301739 org.eclipse.mylyn_feature - 3.24.2.v20180905-0003 org.eclipse.ocl - 3.1.0.v20110606-1427 org.eclipse.pde - 3.13.300.v20181206-0815 org.eclipse.platform - 4.10.0.v20181206-0815 org.eclipse.rcp - 4.10.0.v20181206-0815 org.eclipse.tm.terminal.connector.local.feature - 220.127.116.11811011802 org.eclipse.tm.terminal.connector.ssh.feature - 18.104.22.168811011802 org.eclipse.tm.terminal.connector.telnet.feature - 22.214.171.124811011802 org.eclipse.tm.terminal.control.feature - 126.96.36.199811011802 org.eclipse.tm.terminal.feature - 188.8.131.52811011802 org.eclipse.tm.terminal.view.feature - 184.108.40.206811011802 org.eclipse.userstorage - 1.1.0.v20170526-1605 org.eclipse.wb.core.feature - 220.127.116.11812270937 org.eclipse.wb.core.java.feature - 18.104.22.168812270937 org.eclipse.wb.core.ui.feature - 22.214.171.124812270937 org.eclipse.wb.core.xml.feature - 126.96.36.199812270937 org.eclipse.wb.doc.user.feature - 188.8.131.52812270937 org.eclipse.wb.layout.group.feature - 184.108.40.206812270937 org.eclipse.wb.rcp.SWT_AWT_support - 220.127.116.11812270937 org.eclipse.wb.rcp.doc.user.feature - 18.104.22.168812270937 org.eclipse.wb.rcp.feature - 22.214.171.124812270937 org.eclipse.wb.swing.doc.user.feature - 126.96.36.199812270937 org.eclipse.wb.swing.feature - 188.8.131.52812270937 org.eclipse.wb.swt.feature - 184.108.40.206812270937 org.eclipse.wb.xwt.feature - 220.127.116.11812270937 org.sonatype.m2e.mavenarchiver.feature - 0.17.2.201606141937-signed-20160830073346 org.sonatype.tycho.m2e.feature - 0.8.1.201704211436 org.testng.eclipse - 18.104.22.168908240652 org.testng.eclipse.maven.feature - 22.214.171.124908240652 org.testng.p2.feature - 7.0.0.r201908191551 tern-feature - 126.96.36.199903271146 tern-jsdt-feature - 188.8.131.52903271146 tern-linters-feature - 184.108.40.206903271146 tern-server-nodejs-feature - 1.2.0.me201904021204 tern.eclipse.ide.server.nodejs.embed - 220.127.116.11903271146 Eclipse startup command=-os win32 -ws win32 -arch x86_64 -showsplash -launcher C:\MyEclipseCI\myeclipse.exe -name Myeclipse --launcher.library C:\MyEclipseCI\plugins\org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.900.v20180922-1751\eclipse_1801.dll -startup C:\MyEclipseCI\plugins\org.eclipse.equinox.launcher_1.5.200.v20180922-1751.jar --launcher.overrideVmargs -install C:\MyEclipseCI -data c:\eclipseWorkspaces\EQA -showLocation -vm C:/Program Files/Java/jdk1.8.0_191/bin\..\jre\bin\server\jvm.dllSeptember 3, 2019 at 10:11 am #622914
Some really quick questions:
1) Did you re-enable CodeMix to take the update? Or did the update take place automatically? Is CodeMix now enabled after the update?
2) If CodeMix is enabled, does disabling it make any difference?
3) Can you please see my post here about uninstalling the Icon Designer if you have DevStyle installed? If you do have it installed, please follow the steps mentioned in this thread and let us know if it makes a difference.September 3, 2019 at 1:11 pm #622952
Hi Brian –
Responses to your questions:
1) I did not re-enabled CodeMix – the update happened automatically (or at least, after I selected “review” and update). After the update/restart, CodeMix was not re-enabled.
2) As in above, CodeMix was not enabled, and has not been enabled for a while.
3) I read the post you referenced. I disabled “Startup Experience” in the DevStyle preferences, and that made no difference in reducing startup time. I looked in the installed software (“Help/Install from site…”), and I do not have the Icon Designer installed.
I continue to see ~3-4 minute startup times.
— ToddSeptember 4, 2019 at 7:23 am #623178
Did you read the Windows Defender blog post I referenced at the start of this thread?
Sorry I have to explicitly ask about this because it would explain why you see increased startup time, only after taking the most recent CodeMix update. We now pack the CodeMix engine into the CodeMix plugins, because of which Windows Defender, if enabled, has even more to scan in your MyEclipse installation and could adversely affect startup time.
If it’s not Windows Defender, can you turn on the workspace selection prompt (if not already on) and let us know if you see most of the time taken to get to the prompt or post the prompt, after a workspace is selected?September 4, 2019 at 1:00 pm #623270
Hi Brian –
I did see that reference. I’m not running Windows defender – our shop uses “AVG Business” (I posted in another thread – https://www.genuitec.com/forums/topic/latest-myeclipse-updates-triggers-anti-virus-block-2 – about an issue I found there).
I normally start MyEclipse from a shortcut, with the target looking something like this: “C:\MyEclipseCI\myeclipse.exe -data c:\eclipseWorkspaces\testWorkspace -showLocation”
Just now I started MyEclipse via double-click in the Windows Explorer. Almost all of the wait time was in the splash dialog, waiting for the workspace selection dialog to open. About 2-3 minutes. Once I selected a workspace, I waited ~20 seconds for the IDE to open and settle.September 9, 2019 at 3:25 am #623763
I’ve disabled everything you advice, added the exception on windows defender. It takes 5-6 minutes to start. It is really a painSeptember 9, 2019 at 6:18 am #623780
a) We’re actively researching this issue based on your reports. Apparently a recent change to Windows / Windows Defender seems to have made the process exclusion outlined in the article ineffective.
The working solution right now appears to be excluding the folder in which MyEclipse is installed from Windows Defender, as opposed to a process exclusion. Can you please try this instead and let us know if it helps?
I want to reiterate that we’re still looking into what is going on with Windows Defender and will update this thread accordingly.
b) I’ve asked a couple of additional questions in my post which you haven’t answered, would appreciate some explicit answers because we’ve been unable to replicate issues beyond Windows Defender so far.
1) If you shut down MyEclipse and start again in the same session, does it still take the same amount of time?
2) Can you both try switching to a blank workspace to see if the workspace and/or the set of projects you’re working with is causing the slowdown? – I’m assuming this did not make a difference.
3) Any additional plugins added to the installation?September 9, 2019 at 6:28 am #623783
Just now I started MyEclipse via double-click in the Windows Explorer. Almost all of the wait time was in the splash dialog, waiting for the workspace selection dialog to open. About 2-3 minutes. Once I selected a workspace, I waited ~20 seconds for the IDE to open and settle.
This sounds just like what Windows Defender does, it’s likely that AVG is doing something similar, scanning the installation before allowing it to execute. You may have already tried this, but if not, would it be possible to temporarily disable AVG and see if/how that affects startup speed?
We’re getting set up here to start testing with AVG and a few other A/V solutions as well.September 9, 2019 at 9:24 am #623826
I disabled AVG, and saw 2.5 minutes from splash screen to IDE/workspace. So no change.
I forgot to mention that I placed the c:\MyEclipseCI directory in the scan exception list a while ago, to apparently no affect.
— ToddSeptember 19, 2019 at 3:59 pm #625363
For reasons unknown to me, startup seems to be back to a reasonable 20-30 seconds from splash screen to workspace for the past couple of days. I think that the only thing that has changed on my end is that I uninstalled the latest Groovy for Eclipse, though I can’t be certain that this was a contributing factor to slow starts.October 4, 2019 at 10:43 am #627259
Thank you for the update – we did experiment with Groovy for Eclipse a fair amount, but it had no effect on performance as far as we could see.
As I stated earlier, we now recommend doing a folder exclusion instead of the process exclusion if you’re using Windows Defender, and our blog post https://www.genuitec.com/stop-slow-eclipse-myeclipse-startups/ has been updated to reflect this. If this hasn’t helped, we’ll he happy to have a meeting with your team so that we can see and debug the issues first hand.