All of a sudden the code completion and suggestion (for example when typing the . operator listing the possible methods on an object, etc.) is very slow, also fixing imports. Restarting the IDE didn't solve it.
I cannot see any other task NetBeans is running.
What can be the cause?
Is it because the update to 12.4 is coming up and NetBeans gathers some data or metrics :)
Otherwise the IDE is working normal, quick as usual.
Check if the performance is same when you deactivate your antivirus
Check in the About window of NetBeans where your cache directory is located and rename/delete it
You can try it with most recent release 12.4. It's not yet published on their website but you can download it anyway: https://www.apache.org/dyn/closer.cgi/netbeans/netbeans/12.4/netbeans-12.4-bin.zip
Related
Pycharm, and evidently the JetBrains IDE in general (due to a similar problem with IntelliJ), has difficulty with mundane operations, like opening a project. Specifically, aside from taking a good deal of time to reindex, it actually takes forever, as in never finishing, and freezing or slowing the entire computer's system in the process of "updating python paths".
On the recommendation of a fellow developer, and also related SO (Stack Overflow) post Why is IntelliJ IDEA hanging on "Indexing"? , I followed the advice given:
"In the File menu, select Invalidate Caches / Restart... and then click the Invalidate and Restart button."
And the caveat left in the comment:
"This worked for me but you have to be quick as if you can't get to the menu fast enough it freezes again."
There is also this from JetBrains
Nothing really special in code, but there are a substantial number of imports that are part of the project, including many pip loaded libs. Also using a virtual environment, but owing to the above discussion, don't believe that has bearing on the difficulty. There are other project dependencies, but again, I don't think any are circular (I know Java IDE wouldn't allow), couldn't vouch for third-party libs. Have not experienced similar occurrence working in Eclipse, but unable to shift project work there presently. Using Pycharm Pro 2018.2.7 on Mac OSX 10.13.4
Just run of the mill import statements:
import python-logstash
One expects a project will open in an IDE without crashing one's computer. Having to open twice or thrice or more each time a project is closed (following the menu File, Invalidate caches/Restart...) is weird in paid software, for a known issue. And there is also always the race to run reopen before computer freezes.
Doesn't happen on a very simple project. What is the trigger? Will JetBrains ever fix? Can one change code or imports to avoid?
My Netbeans has been insanely fast for over 2 years, until this morning. Something strange, however, is now happening. Every time i press "copy and paste" ... so CTRL-C, it goes slow. This is what I see:
So, the moment I press CTRL-C, that shows in the bottom, my entire machines goes into super slow mode, and then 5 seconds later it stops.
I've considered maybe there's a keylogger on my machine, but can't find anything. And it's only slow when I copy and paste from Netbeans, nothing else. Maybe Netbeans is sending data out some other way?
Any ideas why Netbeans would just go slow like this?
UPDATE
I only have one project open
I've disabled the git and subversion plugins
I am working on a Laravel project
It's slow when I copy from a VIEW or when I copy from a CONTROLLER (I know css files often go a bit slow because of Parsing, so I figured mentioning this is probably worthwhile)
I followed the advice at the end of this article: here and uninstalled "BlueStacks". Problem solved.
UPDATE
Just in case the article gets deleted, here is the advice the user gives on that page:
I meet the same problem. When I copy a word in the IDE, the IDE does not response until 2 or 3 seconds. I did not confront this problem until few days ago. I try to use the latest netbeans and the latest jdk, but that does not work. Then I find someone said http://bugs.java.com/bugdatabase/view_bug.do?bug_id=5078787 is the problem. And the problem is somewhat about the COM in windows. So I try to install the netbeans to another Win7 PC, and the problem is gone. In that case, I guess the problem is not the netbeans, but some other application in windows. Later I uninstall some of the application I just installed few days ago. And the IDE works right now. The applications I uninstalled is "imc studio" "imc license manager" and "blueStacks" an android simulator. I guess these application may have influence to the COM of Win7. Hope my solution will help to this bug.
You can also just stop the BlueStacks Agent process from Task Manager while you're using NetBeans.
I've been having problems getting debugging working with this setup for the past year. Supposedly, this is fixed in the latest versions, but I just can't seem to get it to work.
I'm using Mac OSX 10.8.5, Eclipse Keplar, PyDev 3.0.0, and Google App Engine 1.8.8.
I set up a run configuration to point to dev_appserver.py, running my project. That works fine. My python version is 2.7.3, and everything works in normal mode. When I try to run in debug mode, however, the app runs, the output specifically states:
pydev debugger: starting
pydev debugger: google app engine integration enabled
But after 20 seconds, the python process terminates with this error message:
'Launching New_configuration' has encountered a problem.
Timed out after 20.0 seconds while waiting for python script to connect.
Accept timed out
Execution works during those 20 seconds, because I can hit URLs connected to my app and see an effect. Breakpoints do not work, though. Is there something I need to do to get python to 'connect'?
Also - I should note that switching back to using 'old_dev_appserver.py' fixes this problem - debugging works fine when I do this. But, this is not really a solution, because I need to use the latest socket additions in the newer releases.
Thanks for any advice.
temporary solution:
edit the pydev_app_engine_debug_startup.py file:
eclipse/plugins/org.python.pydev_${VERSION}/pysrc/pydev_app_engine_debug_startup.py
change the line that reads:
if ':' not in config.version_id:
to:
if ':' not in config.version_id or config.version_id.startswith('default:'):
Looks like this is fixed in 1.9.0. I also had to make sure to update PyDev to the latest (3.3.3 at the time of this writing).
One more thing to add, and this one really tripped me up (on MacOS) -
In Eclipse, under Run -> Run Configurations, set the Main Module to point to this location:
/usr/local/google_appengine/dev_appserver.py
NOT the symlink:
/usr/local/bin/dev_appserver.py
Well, finally I found the answer. It is a Google's bug.
It has been reported and acknowledged.
see Debug is not working with PyDev again 1.8.8!
Update: Until the bug is fixed I am using PyCharm. The pro version has 30 days trial and works with GAE. It works like, well, a charm. I may even consider switching to it from Elicpse/PyDev
But I am used to JetBrains tools with Android Studio recnetly, and WebStorm and Resharper in the past, so I know to find my way around their IDEs. Your milage may and will vary.
Since the question, a new GAE has been released 1.8.9
Running GAE 1.8.9 with PyDev3.3.3 on Windows8.
This timeout issue still occurred.
When I entered the temporary workaround changes to pydev_app_engine_debug_startup described in the earlier answer, then the browser could not connect to the app.
However, on backing out this change, not only did the 'Launching New_configuration' not appear, but the breakpoints worked.
More info on the Python Tool Support for the App Engine Development Server is here
https://docs.google.com/document/d/1CCSaRiIWCLgbD3OwmuKsRoHHDfBffbROWyVWWL0ZXN4/edit
I am having a small problem with plugins not staying installed with Coda 2.2 for Mac on OSX 10.6. Every time I close Coda and open it back up and then click on plugins half of them are gone even though the are in the plugins folder for the application. I have to close Coda and uninstall and reinstall the plugin then open it back up. That is only good until I close it then it starts all over again. Is there anything I can do or is there something I am overlooking that is causing this to happen?
-Thanks
I've been working with Panic support and we've discovered there's an issue with certain plugins. Most likely, it's only one that's problematic. For me, it was WVCPs plugin. Removing that from the plugin folder allows all other plugins to work fine.
I found it helpful looking at the Console app for messages from Coda and one by one dropped the plugins back into the plugins folder until I found the one that caused an error about incompatible architecture.
You can ignore the error about two plugins implementing the same class, that seems to be a mutual exclusion sort of warning but still allows the other plugins to work.
One other plugin had a different error but again, appears to work fine so probably it was just a warning.
This is probably your best solution until Panic push out an update, which I am assured is on the way.
Hope that helps!
I searched lot about this topics but can't find a proper solution.
I am using eclipse 3.6 Helios version with operating system fedora15. In my application I am using GWT2.4 for front end development.
Now while I work with debug mode and want to debug at some point at the same time eclipse hangs for 3-4 mins.It resumes after and again start to debug process.
I am using this eclipse from last 3 years with windows but not faced this issue.In fedora I am using it from last 4 months and this problems stated to occur from last one month.
I am not getting what is the issues with eclipse.
Please help me out.
Thanks in advance.
Is this something that happens with different projects/code, or is it the same code that causes freezes? I've had issues where threads have started in the background and caused problems.
You say "(...) hangs for 3-4 mins.It resumes after and again start to debug process.", what do you mean? Does it continue to debug and move to the next line, or is there a crash and it restarts?
How long has it been since you changed workspace? I've found this, rather than the Eclipse installation, to be an issue over time. Create a new workspace folder, export all your projects and preferences and start fresh.
You are using GWT 2.4 and I think you might be working with UI.xml too... There is a tag in each ui.xml at the top like
<!DOCTYPE ui:UiBinder SYSTEM "http://dl.google.com/gwt/DTD/xhtml.ent">
Which means eclipse is going to get that xhtml.ent file each time and there is a issue in GWT eclipse plugin have a look to below link
http://code.google.com/p/google-web-toolkit/issues/detail?id=5265
There is one comment which says
For me, removing
SYSTEM "http://dl.google.com/gwt/DTD/xhtml.ent"
and saving the document,
solves the problem..
maybe it is needed for something, so better you copy that locally somewhere, and link that.
Try it out and let me know.
I had experienced the exact same problem on a less-powerful notebook I had to use.
Try one of the following
Download the latest Eclipse version (It needs, just as helios, a lot of RAM and CPU because it's based on a new "architekture", in contrast to, for instance, galileo)
Make sure you are using the latest JDK and JRE
Download Eclipse Galileo, which does require pretty less resources and goes still very very fine with most projects!
It sounds like you are experiencing the features of the latest Eclipse arch. In the latest versions of Eclipse I have noticed that the more plugins and add-ons you have installed, the slower the environment runs. There are a lot of similar posts regarding performance on the new platform
I have removed all but the plugins I am using and never install anything not needed into the Eclipse environment.
I "may" have experience this. Not sure. Suddenly started working again. I was getting a hang every time I would try to debug an app, in the part of the code (inside GWT) that creates a "table" element. Could be that there is something that just takes a while and you just have to "wait it out" the when it happens. Go get a cup of coffee, type thing. anyway I HAD stepped deep into the GWT code, plenty so I'm convinced it IS a GWT issue of some kind.
I was thinking it was some infinite recursion possibly in the logging system (like logger code accidentally trying to log itself, and going into loop?). Also there's a 50/50 chance that it was simply clicking on 'run' instead of 'debug' made it start working again. So at least try that if you have problems. My gut instinct and 30yrs programming under my belt tells me it's logger related. I can rule out "slow computers" because I never had this happen until I got a new machien which is Dell XPS, Core i7, 8 GB ram, and massive disk. So I wouldn't blame hardware, or Eclipse bloat.