I'm not sure if this is the right place for this question, if not, please direct me to the right pleace.
At work, we are using Eclipse inside of our remote Citrix machines. Because of this, the workspace is located on a network drive. When doing something for the first time after launch, for example right clicking a project, Eclipse always freezes for a couple of seconds. I think this is because of the delay from the network drive, because it works normally each consecutive time.
Is there a way to cache the entire workspace into RAM at startup to avoid this issue?
Related
I'm setting up a new machine and want to have as much synced between my two machines as possible. I use vscode as my main editor and would like, if possible, to have the two instances synced. I'm wanting to copy some settings folder to my iCloud drive, and then symlink it back to it's location on my local drives.
If I did this, will open files sync in real time, or only on startup? Will this likely lead to anything being corrupted? Is this even possible? Finally, what folder must I sync?
I'm doing exactly this nowadays (after using Settings Sync for a while) – syncing settings via my iCloud folder.
The content of ~/Library/Application Support/Code/User is what you are looking for.
I linked keybindings.json and settings.json and they both work fine without hickups so far. You might want to sync the folder snippets too.
workspaceStorage makes no sense to sync because they are specific to the workspaces you open on a single machine.
It works basically "out of the box". Even if a new setting gets not picked up instantly by a running VSCode instance if it syncs in the background while open, you can always cmd+shift+p Reload Window or open and close the settings (I almost never have to do this).
I would like to take a step backwards opening eclipse without it automatically opening the source files which were last open, nor the projects which were last loaded, I have reason to believe this might clear it all up.
Motivation being that as of a forced quit of eclipse, after it had gone stuck after some project changes, my eclipse Luna is no longer able to start without getting hung up again.
How may I accomplish that?
It's important to me not to lose my settings such as syntax highlighting and stuff, while performing the salvation... and whereas I am pretty certain I could locate my workspace directory on disk, would be nice finding where does eclipse keep the pointer to it, just to make sure I'll be tinkering with the right workspace, if needed..
I guess I could call it "starting eclipse in safe mode" :)
Occasionally, my fingers are faster then my brain and accidentally close views or windows of my development environment (which is Eclipse Kepler). I usually have two windows of Eclipse running side by side with individual views configured in both of them. Unfortunately, as soon as I (unintentionally) close a view/window, I have to set it up again. E.g. the build files in my Ant view get lost, I have to reopen files and so on...
Generally speaking, are there any plug-ins or options you can recommend that can help me backup and restore sessions? I'm aware of the "Save perspective" feature, but it barely meets my needs.
To be more precise:
Is there any feature to make Eclipse request my confirmation, before a (top-level Eclipse) window is closed? - I rarely do uncontrolled clicks twice :-)
Is there any plugin to save and restore my current views (incl. build files in Ant view)?
Is there any plugin to save a set of open files I'm currently working on? Would be neat, if I could open several files on a single click and get working right away. I'm thinking of a session management, where I can switch between several sets of open files.
Just in case none of the above is available and I messed up again, are there any files I can copy from one workspace to another to restore my Eclipse setup (windows/views)?
Any hints are welcome.
I am trying to run my projects in Eclipse, whenever I used to run any program a window appear and it shows that project is launching and building.
This never happened before. In fact, it was working very okay an hour before but now, even for old created project it showing this and not moving ahead.
Is this a general thing happened in eclipse as I haven't seen this before.
I want to get out of this to move ahead and to run the project.
The Launcher looks like this :
The progress Bar is also not moving ahead if it's building the project.
It's definitely normal to see; there's times I'll see it two or three times in a day. It shows up if the launching process is waiting on anything or is expected to take more than a couple seconds.
In your case, it seems to be stuck on "Building workspace," which happens when you open Eclipse. The more projects you have in Eclipse and the more sections of workspace you have (groups of tabs), the longer it takes to build your workspace. So I'm going to wager a guess that you tried to launch a project within the first minute or two of Eclipse being open. Am I right?
If that's the case, just wait a bit, and watch the lower right corner (where it says "Launching Clock" in your screenshot). When it shows it's stopped trying to do start-up tasks, you should be good to go.
If Eclsipse had been open for a while, then perhaps Eclipse is busy with other junk and calling it "Building workspace." Maybe it's having a hard time understanding what to do with one of your projects, so check for compiler errors. You can also try to "clean" your projects (Project -> Clean).
If that also fails...hmmm...I'm sure there's other options before you get to this point, but you might need to re-install Eclipse. I suppose there's a chance that in the deep dark corners of Eclipse, a file was corrupted, causing Eclipse to hang on a task that requires a missing/bad file. But before you go this far, make you get second or third opinions, because I might be missing some simpler cause of your Eclipse hanging than what I've listed already.
I found the solution.
I don't know what was the error and why it was displaying the Launcher window and stuck there. But, I forcefully stopped eclipse using Task Manager and then restarted it.
When restarted it took few minutes (more than usual time) and I was done with it. now it's working okay.
Re-installation of Eclipse also worked but i tried this before re-installing or upgrading.
I've been using Eclipse without issue (I mean, besides the usual) for several weeks now. It's been speedy enough for my purposes. But as of today around noon, anytime I start typing an HTML tag or other autocomplete-able element, my whole System bogs down so much it's completely unusable. Watching in Task Manager, I show that Eclipse jumps from 0 up to 10-15% every time I type a "<" or ">" symbol!
I have a Core i7 PC with 6 GB of RAM, so this definitely isn't a system specs limitation. I've also uninstalled a couple of programs I installed today hoping maybe one of them was conflicting, but no dice. Even after a restart, I am unable to use Eclipse without pausing for several seconds every time it tries to auto-complete!
Anyone know what's going on here? I did some searching but all I found were VERY old bug reports that say the developers "are aware of the issue and are working on a solution".
First, I'd try bumping up the memory that eclipse has allocated to it:
-vmargs
-Xms2048m
-Xmx3072m
-XX:MaxPermSize 128m
That should be in your eclipse.ini file. This blog has some great reading as far as memory and Eclipse are concerned. Also you can read this lengthy SO thread if you need some more info and / or wish to induce sleep.
Next, try speeding up autocomplete. Go to Window / Preferences / Java / Editor / Content Assist / Auto-Activation and decrease Auto activation delay from 500 to zero.
Finally, you might look into hippie complete; the default key binding in Eclipse is 'alt-/' . This is also called "Word Completion" if you check out the shortcut list 'ctr-shft-l' ( that's L as in list ). On my mac the default key setting is 'ctr-.' . This is a faster version of autocomplete that I believe harkens back to the days of emacs. It seems to work great with local variables but not so great with functions on objects. Different beast I guess.
As a bonus, you can check here for a list of ways to speed up the Eclipse experience in general.
First, just as a test, try switching to a new workspace (File → Switch Workspace → Specify a folder which does not exist, it will be created).
If the problem is solved, this could be an issue with some bad settings or cache in your current workspace. If you can easily move to this new workspace (don't know how much effort you've put in customizing your workspace), I'd do that.
If you want to fix your current workspace, go into the .metadata/.plugins folder of your workspace, and look for folder that start with org.eclipse.wst. I'd try to take them out, and see if it helps (close Eclipse first). You may lose mostly history and cache in the process. You can check the folders specifically and intelligently guess what should stay.
If the problem is not solve by changing workspace, I would try downloading a fresh copy of Eclipse. You could try to reset the configuration folder, but that's a bit risky. If it's too much trouble, I'd start fresh.