- This topic has 11 replies, 2 voices, and was last updated 11 years, 10 months ago by
.
-
Posts
-
Hi there,
I finally have updated to MyEclipse 10.7.1 and I noticed a huge impact in performance, to be worst.
I would like to know if there is a way to go back and use the previous version. I prefer to have to reconfigure some things and go faster than solving this issue and go into another one.
I’m launching a Java script and it lasts about 2 minutes to launch!
EDIT: More information
It stucks verifying launch attributes and then with every single step.
anlagmat,
No changes were made to any areas that would result any additional slowness you described – I would presume that something else is wrong with your configuration. We have also rigorously tested this release. Just for a sanity check, could you try a new workspace?
Re: launch a javascript and launch configuration issues; can you please describe the steps you are taking in detail so we are on the same page? I’m not sure what yo mean by “launch a javascript” or which launch configuration you are talking about exactly.
There is no way to downgrade from within the product, you can use an offline installer from our download page (the 10.7.1 installers have still not been uploaded) to install another copy of 10.7.0 and open your existing workspace with it.
@Support-Brian wrote:
anlagmat,
No changes were made to any areas that would result any additional slowness you described – I would presume that something else is wrong with your configuration. We have also rigorously tested this release. Just for a sanity check, could you try a new workspace?
Re: launch a javascript and launch configuration issues; can you please describe the steps you are taking in detail so we are on the same page? I’m not sure what yo mean by “launch a javascript” or which launch configuration you are talking about exactly.
There is no way to downgrade from within the product, you can use an offline installer from our download page (the 10.7.1 installers have still not been uploaded) to install another copy of 10.7.0 and open your existing workspace with it.
Hi Brian,
When I refer to a Java script I’m referring to a Java, script, not a JavaScript. When launching, and passing parameters it lasts forever.
I’ve tried with another workspace and downloaded it from SVN so I think that’s not the issue.
Could be that I have installed Java 6 ?
anlagmat,
So you’re talking about launching a standalone Java application? Passing parameters = editing parameters in the launch configuration wizard or actually working in your application.
MyEclipse does ship and run with Java 6 by default, this would be the case with 10.7 as well, with the same JDK. Installing an additional copy of J6 on your machine (I’m assuming that is what you have done) would not affect anything unless you configured your workspace to use that JRE, and even so – should not cause a slow down.
I’m sorry but I asked for the steps you are taking to reproduce this problem because your description of the issue is ambiguous. If you could list out the exact steps, we may be able to provide better assistance.
Brian,
I don’t know how to reproduce the issues. They just happen. I’ve left that project so I’m with a IceFaces one. I receive a lot of leak messages from Eclipse and it recommends me to restart the program, I do, because if I don’t it becames unmanageable.
Just an example, random. Today I’ve tried to open a properties file and… NullPointer exception.
java.lang.NullPointerException at org.jboss.tools.common.model.project.ProjectHome.getLocationFrom_strutsstudio_File(ProjectHome.java:61) at org.jboss.tools.common.model.project.ProjectHome.getLocation(ProjectHome.java:52) at org.jboss.tools.common.model.project.ProjectHome.getLocation(ProjectHome.java:38) at org.jboss.tools.common.model.project.ModelNature.checkModelNature(ModelNature.java:220) at org.jboss.tools.common.model.util.EclipseResourceUtil.getModelNature(EclipseResourceUtil.java:218) at org.jboss.tools.common.model.util.EclipseResourceUtil.getObjectByResource(EclipseResourceUtil.java:93) at org.jboss.tools.common.core.resources.XModelObjectEditorInput.convertFileInput(XModelObjectEditorInput.java:197) at org.jboss.tools.common.core.resources.XModelObjectEditorInput.checkInput(XModelObjectEditorInput.java:174) at org.jboss.tools.common.editor.NatureChecker.isAppropriateNature(ObjectMultiPageEditor.java:1225) at org.jboss.tools.common.editor.NatureChecker.check(ObjectMultiPageEditor.java:1213) at org.jboss.tools.common.editor.ObjectMultiPageEditor.init(ObjectMultiPageEditor.java:91) at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:828) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:647) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:289) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2945) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2850) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2842) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2793) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2789) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2773) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2764) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:651) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:610) at org.eclipse.ui.internal.ide.handlers.OpenResourceHandler.execute(OpenResourceHandler.java:129) at org.eclipse.ui.internal.ide.handlers.OpenResourceHandler.run(OpenResourceHandler.java:181) at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute(ActionDelegateHandlerProxy.java:289) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1262) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1104) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1100) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1509) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4640) at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:345) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4528) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4972) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2531) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410)Now I have to restart the software again.
Here you have my error.log available to download: https://mega.co.nz/#!4wdBwRYJ!Ru6ZiRxkeUsj4MWsHl3emDPUArli5C79V1nesVLThEw
After switching workspaces, deleting metadatas and all that stuff… I realized that the problem arised after trying to open a .properties file.
I changed the File association so it won’t use the MyEclipse default and instead use the Properties File Editor.
Moar errors…
I’ve noticed than when starting/stoping my Tomcat from MyEclipse, sometimes this kind of messages appear:
Unhandled event loop exception
unable to create new native threadAnd then, appears the following dialog:
Seriously, I cannot work. It’s both frustrating and annoying as hell.
It fails every few step as I save, press F3 to go to a method, or restart a Tomcat. I have several colleagues that are working just good with 10.6. Why don’t you offer some kind of downgrade?
Do you have any solutions / response ?
It’s kinda frustrating. I’ve disabled all validations and now I’m able to work with less messages but it’s still giving me errors. I’ve checked the memory that uses and it’s not over 400 Mb and my .ini settings are as follows:
#utf8 (do not remove) -startup ../../Common/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.library ../../Common/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_4.2.0.v201201111650 -install C:\Users\anlagmat\AppData\Local\Genuitec\Profiles\MyEclipse 10 2 -vm C:\Users\anlagmat\AppData\Local\Genuitec\Common\binary\com.sun.java.jdk.win32.x86_1.6.0.013\jre\bin\client\jvm.dll -configuration C:\Users\anlagmat\AppData\Local\Genuitec\Profiles\MyEclipse 10 2\configuration -vmargs -Xmx1024m -XX:MaxPermSize=512m -XX:ReservedCodeCacheSize=128m -Dosgi.nls.warnings=ignoreSo, what’s wrong here?
anlagmat,
I’m sorry I missed your responses to this thread.
1) We cannot easily offer a downgrade process in the 10.x stream; that’s just how base Eclipse is built. The only way to downgrade would be to use a 10.6 installer and install a separate profile. Please write to brian@genuitec.com with your subscription code and key and I will personally send you the offline installer links.
We are changing our delivery technology in the 11.x stream, that will offer an in-product downgrade too, unfortunately that is not an option right now.
2) As stated before, I doubt your problems are related to the MyEclipse version as no changes have been made in this area, especially between 10.7 and 10.7.1. It would seem that you are indeed running out of memory, but this could be related to the application that you are running. An option is to try to give the Tomcat server more memory on Tomcat configuration page.
Running out of memory even when editing basic Java (like pressing F3) is really uncommon. If you have noticed, do you have any problems before you launch your application in Tomcat or do they only start after starting the server.
3) There are some tips on handling memory issues here:
https://www.genuitec.com/forums/topic/troubleshooting-memory-amp-performance-issues/ – could you please check the second point covering JavaScript?Hi Brian,
Thanks for answering and sorry for my rant. I’m pretty frustrated as it is the tool I use most in my work and I waste a lot of time with this.
1 ) I’ll mail you as soon as my boss arrives and can gives me the subscription code and key.
2 ) I would like to know where my problems come from, seriously. We are about 9 people working in similar projects (same base, different customers) and it seems that I’m the only one with problems. The only notable difference is that they have 10.6 version. I didn’t worked with the Tomcat at all yesterday and still got some crashes and I tend to work with just one application deployed on the Tomcat.
3 ) I have disabled JavaScript but I’m not sure that is the problem since the project just contains 4 javascript files. It was in passive mode.
Thanks for your support.
Antonio,
1) Please let me know what happens if you run with 10.6 and the same workspace.
2) On studying your error log in more detail, it is possible that there may have been some problems with your 10.7 installation itself or the workspace set up as there were some null pointer exceptions with some basic code. Can you tell me how you installed 10.7 – did you upgrade to that from 10.6 and further on to 10.7.1 with the in-workspace upgrade?
3) Certainly does not seem to be JS that is the cause of your issues.
When you aren’t launching your application with Tomcat, what are you doing in your application, specifically – are you primarily editing Java code or do you edit JSPs and HTML files, too? If using the JSP and HTML editors, do you use the visual designers or source only editors?4) How many projects do you have in your workspace – do these have many JAR files on the projects’ classpaths?
I can understand being frustrated when your primary work environment is problematic; we certainly appreciate your help in tracking down the problems.
