Eclipse hangs on copy/cut for JavaScript files

found the solution:

go to Window>Preferences>JavaScript>Editor>Mark Occurrencesand unselect the checkboxes. That should do it.

Reason for this problem:

When u press ctrl for copy/paste, it assumes that is a "ctrl+mouseOver" operation, that we do before clicking on a method/variable name to reach its declaration point, or access its documentation. Hence, it tries to find all the occurrences of the text currently under the mouse cursor, along with its declaration point and documentation.

Hope this helps :)

Navigate to Window -> Preferences -> JavaScript -> Editor -> Typing -> When pasting

then uncheck Update imports.

Performance improved tremendously in my case. Hat tip to the comment left by @Alexander Taylor.

This is first Nodeclipse performance related issue I hear.

I think memory usage limits are to insure that bad routines don't eat memory without stop (and affecting all operating system performance). Usually eclipse takes 200-400MB. If your eclipse average is above 500MB I guess you installed too many plugins into 1 Eclipse instance.

Raise an issue for Nodeclipse developers https://github.com/Nodeclipse/nodeclipse-1/and give exact OS, Java, Eclipse, Nodeclipse versions. Also because it is performance issue you should give your PC configuration CPU, RAM size. Without that exact information it is impossible to investigate. You can also try yourself on other PC, other Eclipse version, other Java version etc and compare, find best combination. Please raise an issue even if you discovered solution yourself.

Read http://www.nodeclipse.org/ carefully. (You should have read before using for at least to learn some tips, and how to get help.) I am not sure it is Nodeclipse issue, but if it is reproduce-able, then it is to be solved quick or Eclipse bugzilla bug to be raise if it is some Eclipse project related.

For information (as of Nodeclipse 0.10)
1) Nodeclipse has 2 Editors: JSDT-based and TextEditor-based. Both have code completion. Trying TextEditor-based can tell if the issue is JSDT related.
2) For validation JSHint validation is used. JSHint is run on Rhino engine that is not so quick, and potentially can take time on large projects. However JSHint Integration is quite mature project and there are options to stop validation after certain number of warnings.