I am using Eclipse Neon.1 on Windows 10 with Redhat JBoss Developer Studio to work on a JavaEE 7 Project running on Wildfly 10 via jdk1.8.0_25.
The Project has about 20.000 lines of Java source and also about 20.000 lines of .xhtml source code.
All in all, Eclipse performs quite well. Except the Xhtml Editor.
Once I start to edit .xhtml files, Eclipse freezes up all 5-15 mins for about 30 sec. This happens only while using the Xhtml Editor. Java or other Editors do not show that behavoir.
I tried the default Html Editor and the JBoss Tools Html Editor. Both show the exact same behavoir.
I searched the web and tried some solutions like switching off automaitc build, source link navigation and validators. Nothing of that changed the behavoir.
So I started to watch the Eclipse Process in JVisualVM. At times when the Editor freezes, there is full CPU load on one Core, no GC activity and plenty of Memory left. So I would say its not a general problem with Memory or the GC.
How can I find out what exactly causes these freezes? Maybe someone knows this very issue?
Are you using devstudio 10.2 as installed from Eclipse Marketplace (or other update site) into an existing Eclipse Neon.1 install?
If so, you could try playing with your memory settings in eclipse.ini. Or, try using the devstudio installer, which will give you different memory settings in devstudio.ini.
https://developers.redhat.com/products/devstudio/download/
If you're not already on devstudio 10.2, you could try updating to the latest.
But if it's NOT a memory problem... then you might want to report this as a bug in JIRA here:
https://issues.jboss.org/secure/CreateIssue.jspa?pid=10020&issuetype=1 using component = jsp/jsf/xml/html-source-editing
Could you also attach a sample project or .xhtml file to that JIRA, which causes the freeze, so someone can reproduce your issue?
Related
I am having slight difficulties as of late with my eclipse installation. Necessary Background information: We decided to use a specific version of the Spring Tool Suite (3.8.1 to be precise) with a specific set of plugins as our common developing environment.
So what we did is this, we fetched the 3.8.1 STS, modified the default config so work with our gradle plugins and then repacked that so it could be easily distributed in our network.
After this, we installed the plugins in one of the clients and then pushed the plugins and dropins folder onto our network share as well, so we could easily update the plugins without having to repack the entire thing every time we decide on a plugin upgrade.
This worked fine on almost all machines, except one, but we this that has something to do with the fact that the user in question has a second version of the Spring Tool Suite on his Computer.
However, roughly 2 days ago, I had to reset my installation because I carelessly updated too many modules and was unable to use the installation history to revert to the previous setting.
After I removed my current installation and purged the workspace, I reinstalled, reimported my projects and tried to work. This went fine until I tried to open a Spring Bean Configuration xml file with the provided Spring config editor - My IDE showed just an empty tab without title or content. After that, I tried to open the same file with any other internal XML editor, all showed the same - an empty tab. When creating a new Java Project, all XML Files are opened and displayed correctly though. But as soon as I try to open an XML file with the Spring Config Editor, I cannot open XML files in that project at all - except with a regular text editor.
Plus, sometimes my workspace gets addled by that so it generates an error and prevents eclipse from even starting.
Does anyone have any idea why this could be happening and what to do against it?
More Specs:
STS Version: 3.8.1
Eclipse Version: Eclipse Neon
Plugins: (all fetched on Jan 11, 2017)
Buildship Gradle Integration
Minimalist Gradle Editor
EclEmma & JaCoCo
SonarLint
Eclipse Metrics
Thymeleaf Content Assist
JBoss Community Plugins
A solution here was to use STS -clean, as that cleanes the data one most often misses.
in this case, it was workspace metadata that seems to have caused the error.
I'm seeing these green margins on all of my .xhtml files - in addition, Eclipse seems to be running a little more slowly when the files are first opened.
In addition, Eclipse is updating classloader often and slowly while working in these files.
Any ideas as to what's going on?
How can I fix this?
I'm using Eclipse Java EE IDE for Web Developers.
Version: Luna Service Release 1 (4.4.1)
Just figured this out - figured I'd post in case anyone ran into the same issue. It turns out that Eclipse was opening these files in the Web Page Editor. Once I switched back to the HTML Editor, all issues were resolved.
I recently move to Eclipse Juno from Indigo. Although Juno works perfectly as far as my needs the windows "Open" dialog box does not load for some reason. For example, File/Open File does not work.
This is a problem across all places where we need to include a file like adding external JARs or any other place where files need to be added from a windows directory.
"Include Directory" does work where I need to get the directory included but the issue is only with file dialog box.
I have a Windows 7 64 bit and it’s a Eclipse with Java & CDT plug-in.
Reinstalling eclipse would be a last resort as I would need to re-configure 40+ projects again as we have a very peculiar setup here.
I did try to research this but hardly could find more details.. Any pointers to fix this issue will be greatly appreciated.
Edit:
Just wanted to add that tooltip does not work up when I hower mouse on the different icons/files ect, not sure if this is related but just wanted to mention.
Also, I tried updating my eclipse to Kepler but it still does not work, I am now wondering if my Windows 7 has something to do with this..?
I was able to finally resolve this based on research done in this Eclipse bug. My work machine still has java 1.6.0_26 and this release has a bug related to AWT.
I changed the eclipse's java version to 1.6.0_45 and this issue was resolved. I used -vm parameter in eclipse.ini file in to tell eclipse to use a different version.
I just added JBoss tools and I like a lot of what I get from it. However, I noticed that my .xhtml files are loading a /lot/ slower (on the order of several seconds) than before I installed JBoss tools. I'm willing to accept some slowdown (there's always overhead from using tooling sitting ontop of Eclipse) but this is a pretty long wait. I suspect it has to do with the visual editor that JBoss has added for .xhtml. I am using windows 64 bit and I can't use this editor. I've also tried following the advice at this link
http://docs.jboss.org/tools/whatsnew/vpe/vpe-news-3.3.0.M2.html
and adding -Dorg.jboss.tools.vpe.loadxulrunner=false to the eclipse.ini but I didn't notice any speedups. I also uninstalled the plugin for the JBoss visual editor and didn't see any results. After uninstalling the plugin the visual/source, source, and preview tabs are still at the bottom of the .xhtml editor, so maybe I uninstalled the wrong one?
I'm using Eclipse for Java EE Juno service release 1 Build id: 20120920-0800. I have the CDI, dynamic web module, Java, javascript, JSF 2.1, JAX-RS 1.1 JBoss Maven Integration 1.0 and JPA 2.0 facets installed on this project.
It is hard to say what you just uninstalled.
If you want just uninstall visual editor you can do such thing:
Just install onece again Eclipse and when you install JBoss Tools just doesn't select visual editor
Try to unistall visual editor. I think (but I never tested it) you should remove from plugins and features directoris wich starts from org.jboss.tools.vpe
I don't know if there can be some problems with dependencies and so on - you should make backup of Eclipse directory before making any changes.
Maybe it will be sufficient just open the files with other editor:
You can just open single file using other editor, just click in Package explorer view on the file with right click and choose Open with... menu - then you can open the file with for example HTML editor:
You can change the default editor for all files by open Window->Preferences menu and find Find associations position. There should be *.xhtml extensions - choose it and change the default editor.
I do C++ embedded development for the NetBurner platform. They have plug-ins that customize Eclipse and in addition to a build tool-chain they add a Launch Group under the Run Configuration area. Everything was working fine under Indigo (32 bit) when I decided to install Subclipse (big mistake). As soon as the install finished I could no longer run my existing configurations successfully. When I went into the Run Configurations area I noticed the Launch Group I used to use was missing. Here is what it looked like earlier yesterday:
Here's what it looks like today:
Things I've tried
First I uninstalled the Subclipse plugins using the
Help->About->Installation Details and then selecting them one at a
time, Uninstalling and restarting after each uninstall. No change.
Then I unpacked the original Eclipse Indigo/CDT 32 bit download to a
fresh folder. Copied over the NetBurner plugins from the zip I got
from the manufacturer. No change.
Launched with different Workspaces, no change.
Launched a Galileo version, it uses older plug-ins, and it still
works.
Copied older plug-ins into Indigo, the older NetBurner launcher
shows up (but it doesn't really work with Indigo)
Removed the older plug-ins put in the newer ones, old NetBurner
launcher went away new launcher does not show up.
Tried removing the
{Workspace}.metadata.plugins\org.eclipse.debug.core.launches - no
change.
Interestingly even though launches has many .launch files that should show up under Run Configuration, nothing shows up.
One other strange (possibly relevant) thing is that icon for the NetBurner Perspective went away, now it just has <NetBurner> as the text and a generic perspective icon.
I can still cross-compile and build for the NetBurner (i.e. the build toolchain still works), it's just the ability to use run configurations that seems to be missing.
I'm out of ideas, does anyone know of some global setting that sits outside the workspace and outside the Indigo installation folder that could be causing this?
I'm running on Win 7 64 bit ultimate, I run the 32 bit version of Indigo because the 64 bit doesn't appear to work with the NetBurner plug-ins. I've also disabled the two Mylyn tasks under General->Startup and Shutdown (they seemed to cause many Permgen memory crashes). This is the same setup I had working flawlessly yesterday.
Update
I also noticed that only 3 of the 4plug-ins are showing up in the Installation Details plug-in pane. The nbeclipse.core_2.6.0.jar is in the eclipse plugin directory but not showing as loaded. So I guess I know now the problem is the plug-in isn't loading but I don't know why or how to get it to load, or what subclipse could have changed that would cause this.
I suspect that the Subclipse installation may have caused an update to some other plugin(s) that it depended on (keep in mind the transitive nature plugin dependency resolution; if you're installing plugin A and it requires a certain version of Plugin B that you don't have, Plugin B will be installed or updated to that version). In doing so, maybe the NetBurner plugin can no longer load because its declared dependencies are no longer met (ie, it depended on an earlier version and does not tolerate a later version).
You can use the OSGi Console to help determine why a plugin is not loading. Here are a couple of references that should help:
http://grep.elasticpath.com/community/techblog/blog/2010/05/27/eclipse-plugins-and-the-osgi-console
http://www.vogella.com/articles/OSGi/article.html#osgiconsole
By the way, you can not just copy plugins into an Eclipse installation and expect them to work. For several versions now, Eclipse has not supported that ability. You must use Help > Install New Software or File > Import > Install > From Existing Installation to install plugins. Ask the vendor if they have an update site to install from; like I said above, simply dropping things into Eclipse's plugins folder is not supported any more, it won't work. Other than the vendor providing an update site, the only other option is to use the dropins folder, as described here.