After last Ubuntu 14.04 kernel update (current one: 4.4.0-36-generic) when I open Eclipse (Luna) in a matter of few seconds it closes or freezes and then closes (I can be simply editing a comment, or even stop typing for some seconds and then it happens, so I think it can't be related to the code itself).
I personally prefer when it freezes first, so it gives you some seconds to mentally prepare of what is about to happen with your last-hour work.
No clue on system.log or /.../my_workspace/.metadata/.log of what is happening.
Where could I look to try to understand what is happening?
Is it possible that Eclipse closes without leaving any clue/crash-report of why is it doing that?
After trying a lot of possible solutions because Eclipse was crashing every 10 minutes I've found this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=465693
According to this bug report it is not an Eclipse problem but an Eclipse-JRE relationship problem.
Since I've modified several lines in eclipse.ini I cannot be sure about the solution, but it seems it was adding this line on it:
-XX:-UseLoopPredicate
I've been without crashes for more than 1 hour so far. However I'll wait at least one or two days before assuming this solution really works.
EDIT/UPDATE: Confirmed; it works like a charm.
Whenever eclipse crashes you will get hs_err_pid4612.log this kind of file
inside eclipse folder.
For fixing this issue :
Add this to eclipse.ini file:
-Dorg.eclipse.swt.browser.DefaultType=mozilla
Related
I have a problem with my NetBeans. I have asked this question over at NetBeans forum but no one came with an answer. My problem is that everytime I hit enter after writing a bit of code, for example, System.out.println(); and then everything freezes for a second.
This happens all the time. This lag spike/freeze also happens when I write a DOT(.) after something like System.(DOT) then it freezes for a second. This makes NetBeans unusable. I'm running the latest Java at 64-bit and the latest JDK. I have reinstalled the program 2 times and nothing helps. Any idés?
Thanks in advance!
First, I am new to Octave, but fairly familiar with Matlab. After using Octave for a short time I've noticed that the cursor in the command window will regularly add a new, empty line. Sometime this can be in the middle of typing a command. If I let the window sit with no input, the cursor will eventually advance all the way down the page and keep going.
I have never seen anything like this, and I do not know where to even begin to fix it.
Thanks!
Command Window Screenshot
My alternative answer is that that a bug report should be filed so that this issue gets fixed. I have the exact same problem. Every 30 seconds, when system time hits an even minute and 30 seconds past the minute, the command window cursor skips to the next line. One can still type to the command line and hit enter in the end. The command line now split at random points to several lines will be successfully computed. The problem is that you can not edit the line back past the inserted line break and the whole thing looks really messy. I tried to un-install and re-install but that did not help in my case. I use octave-4.2.1-w64-installer.exe
Boring solution (and hopefully permanent): I uninstalled and reinstalled the same version of Octave and this bug seems to have gone away. Not very convenient, but worked for me.
This might be a problem caused by a 3rd party application. I've seen this issue on a computer with Druva inSync. Disabling the Druva inSync service (not the client) stops this. inSync injects itself in applications using the Windows file dialog. Apparently this code contains a bug and accidentally writes a line feed (LF) to a file handle belonging to the application. The problem might also go away with a different Octave version. In particular the 4.2.x and 4.4.x seem to behave differently.
im not sure what i did.. but i am working through some tutorials to get up to speed on python, and i started getting this error message... any ideas on how to fix this? from the error, i looked up the message, and it looks like wham i press the run button it is looking for a file that is no longer there.... but I'm not even working on that file anymore... I'm trying to run something different that does not refer to the previous file.
what does work is if i do run as.. but id rather not do that every time. I'm sure there is a setting I'm just not aware of that i messed up.
Well, not sure how exactly you're getting to that point from your explanation, but please take a look at: http://pydev.org/manual_101_run.html to see how to properly run a module inside PyDev.
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 have had this problems for a couple of times but usually could solve it by an update. However, this fix does not work for me anymore.
Actually, two problems here:
The minor one: I have osX 10.8.3 and Eclipse Juno (M20130204-1200) installed. Since a good amount of time, it takes eclipse ~ 4-5 minutes to start up for the first time after the system start. Once it was closed and is re-opend again, it starts up quick. I think this problem came since apple started to mess around with the JRE? Does anybody also experienced this delay? Could it be that one of the installed plugins checks for updates and causes the delay?
The major one: after eclipse is fully up & running, I can not open .py files anymore. When I open my pydev project (btw. pydev 2.7.3), eclipse freezes and I need to kill the whole thing and restart. -> I can not use it for python coding anymore, which is my primary task...
Suggestions? Re-install eclipse maybe?
Thank you for suggestions,
El
Can't really comment on #1, but for #2, can you try attaching jvisualvm to see what's going on there? (and create a thread-dump and post it somewhere so that I can take a look at it).
I'd ask you to create a bug-report for that, but the new tracker is still not up (I hope I'm able to put it up right after the funding at http://igg.me/at/liclipse is finished).
The problem was resolved by following these steps. They essentially disable one
JRE.http://support.apple.com/kb/HT5559?viewlocale=en_US