We include PyDev in one of our internal RCP applications and it's been well behaved for a while now. Recently I've upraded to 6.3.1 of PyDev, and I have noticed that PyDev appears to be hanging my RCP app when the app is launched in the background. Anytime I launch our RPC with & (background job in unix), we get the app suspended when anything PyDev related happens. As long as we are running in the foreground, things go well, but if the app is running in the background, we believe PyDev operations are causing the app to suspend:
"[1] + Suspended (tty output)"
Situations when hangs occur:
App is running in the background and
we try to set the PyDev interpreter (instant hang)
Occasional hangs when splash screen is up and a org.python.pydev plugin is being loaded.
If any Python editors were open, if we make it to the app running, the open editor will eventually hang the RCP app in less than a minute.
Foregrounding the app always fixes, but it's irritating. I work in a heavily IT controlled environment and our linux http access to the outside world is well shielded. I'm not sure how, but there's plenty of external sites we can't get do (makes everything in open source land very hard to deal with).
So far I have tried (from Stackoverflow and Google):
stty -tostop (did not work. tostop was never set anyway)
Dpydev.funding.hide=1 (did not work)
Djava.net.preferIPv4Stack=true (did not work)
hacking preferences to tell PyDev not to show me popups (did not work)
Piping /dev/null into my app (did not work)
Telling my IT staff "stuff is weird" (did not work and IT had a good laugh)
I have no idea what to do. Telling our users they have to run the application in the foreground if they are using Python scripts is kind of lame and reflects on us, so I'd rather not do that.
Any ideas?
Code completion works BTW. So the majority of hits I get about PyDev hanging do not apply here. We've seen this behavior now with PyDev 5.2 (our old version with Mars) and 6.3.1 (newest version with Neon). So I don't think it's version dependent.
If there's any hacks I can do to PyDev to say "please stop causing my terminal to suspend my RCP app" that would really help.
It's my first post and I have spent most of the time formatting stuff to fool Stackoverflow into beveling that I have not posted code.
Edit:
The log files do not clearly indicate what is happening, although we do see these messages (but they don't seem to correlate 1:1 to the hangs/suspensions)
!MESSAGE The python client still hasn't connected back to the eclipse java vm (will retry...)
!STACK 0
java.lang.RuntimeException: The python client still hasn't connected back to the eclipse java vm (will retry...)
!ENTRY org.python.pydev.shared_core 4 4 2018-04-12 14:06:54.444
!MESSAGE Attempt: 2 of 5 failed, trying again...(socket connected: still null)
!STACK 0
java.lang.RuntimeException: Attempt: 2 of 5 failed, trying again...(socket connected: still null)
Related
I am having problems with setting up the Eclipse IDE for editing source code of SmartHome on Windows 10. I have done everything as it is described in the Setting Up a Development Environment guide.
However everything works until I open up the workbench. At the first start the so called "setup tasks" will be performed automatically which takes about 5 min. After that I still got like 100 errors of 200 items and a bunch of warnings.
In the official guide they say this might be normal. After performing the "manual setup tasks" however (which can be found under "help" in the menu bar) most errors should be gone, which does not happen in my case. Even after rebuilding all of the loaded projects there are still errors and warnings remaining.
Has anybody had similar issues and maybe a solution for that problem?
I've been having trouble getting a weblogic server to run in eclipse, which have resulted in me not being able to open eclipse ni my current workspace at all. It is not my first attempt to work with weblogic servers in eclipse, and I do not know why it suddenly decided to stop working. I have had multiple errors, which all seem to be related to an abnormal high memory consumption.
One of my last errors, before eclipse quit on me for good, was an out of memory exception, on PermGenSpace. I set variables to 1024m, but it still complained it wasn't enough. After a lot of restarts, Eclipse suddenly wouldn't open my current workspace. I have tried others, and they work fine, but with my current one, the splash/loading screen disappears after about 10% of the loading bar is complete, and nothing happens at all. Except the fact that eclipse.exe shows up in the running processes tab on Windows task list. It does not show in the running programs list.
My attempts to start weblogic servers had the exact same symptoms. They showed in the process list, but did not respond when I tried to open the console in my browser.
Both eclipse and the weblogic tasks (shown as java.exe) has had over 400.000KB of memory consumption each, which I find very high.
I do not expect anyone to be able to find a complete solution here, but I am absolutely stuck. I cannot access any of my previous error messages. I have no experience debugging an error like this. Does anyone have any idea on how to find the error in a case like this?
My Weblogic version is 10.3.2, which is a company standard for now.
My Eclipse version is:
Eclipse Java EE IDE for Web Developers.
Version: Kepler Service Release 2
Build id: 20140224-0627
Adding the comment as an answer since it provided some help.
Try starting up to a new empty workspace; If you dont get to select workspace at startup use the argument "-data " If you still get issues, look at the log in /.metadata/.log
I'm having a problem with CCS6, which is based on Eclipse. I'm trying to build a demo project that comes with a TI MSP430 demo board. When I build the project CCS/Eclipse proceeds to clean the project, during which all the memory on my system is slowly consumed. After memory usage reaches 100% Windows declares that CCS/Eclipse is having problems and asks to close it down.
I am running Windows 8.1. I have uninstalled and reinstalled CCS several times, versions 5.5 and 6.0. I get the same behavior every time. I also updated the version of Java on my system. I have reached out to TI support engineers and they are baffled and useless. I have also tried with a second computer also running Windows 8.1, same behavior.
The problem is obviously rooted with gmake somehow. Perhaps there is something wrong with the project files causing this behavior? I haven't experimented with other projects yet.
Thanks!
P.S. I wanted to post screen shots but StackOverflow isn't letting me. The window I see in CCS/Eclipse is titled "Cleaning selected projects" and then reads "Invoking Command: c:\ti\ccsv6\utils\bin\gmake -k clean" And it just stays on this forever. Using Task Manager I can then see my memory slowly filling up. After about 5 minutes or so it reaches 100% use and Windows asks to shut down CCS.
I am running ubuntu 12.04 64 bit, I have set up FB4Linux (FlashBuilder for Linux) and installed the »flash-installer« installer plugin via »apt-get«. I downloaded the latest version of the plugin-debugger from adobe and followed the install instructions from the included README.txt file. Running eclipse (Version: 3.7.2, Build id: I20110613-1736), creating a new as3 project works, build works, everything fine, I can start the debugger and step through the code BUT after a while the debugger just disconnects and stops. No error, no crashes, debug session just over.
Any Ideas?
.log
about:plugins:
Flash - Version: 11.2 r202
Shockwave Flash 11.2 r202
I think , this is happenning more fequently due the enhanced breakpoint listener support in eclipse.When a breakpoint is removed, it is trying to notify its "breakpoint specific" listeners, which were stored in the breakpoint. Of course, this will not work since the underlying marker has been deleted. but things will happen after removing break point. so one way to resolve this problem is to try to un-select
Window > Preferences > Java > Debug : Suspend execution on uncaught exceptions
may this will help you!!
The solution to this issue occurred as side effect after I applied the changes from the answer of this question. When I tried to set the compiler options to target version 11.2, which is actually installed on my system errors occurred because their were files missing in the sdk folder (which are the described changes) and I could only develop for version 11.1. Kind of wired but the update of the sdk made the debugger run stable.
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.