When an error happens while running a RCP-Project, Eclipse shows the location of the error in the Console view. You can click on the filename and Eclipse will immediately opened the file and put the cursor in the correct line.
Since a few days it takes my Eclipse installation very long to do that (several minutes).In the Progress view I see a "Searching" process running and after a long time the file will be opened.
Do you have any ideas what could be the cause of that long duration?
Or how I could find out what Eclipse is doing while taking so long?
===
Update:
Setting up a completely new workspace solved the problem. In the new workspace opening the error location works fine.
I'd still like to know what I could do in such a case to find out what Eclipse is working on (and taking so long for).
I'd imagine that a good jumping off point might be the class org.eclipse.ui.internal.console.FollowHyperlinkAction.
If you set a breakpoint in FollowHyperlinkAction.run(), you could walk down into IHyperlink.linkActivated() and see just what's going on.
Related
I have to deal with this problem periodically. Somehow I'm able to fix it but then it comes back and I forget what I did, so I am putting this out there so that others who have this issue can have some relief and I can find the solution to it next time it happens. Eclipse will lose icons for certain things (right now it is the icon for .jar files) and this causes a Java null-pointer exception dialog box to pop-up if you click on it or Eclipse accesses that resource. It will also lose icons for other things. Here I click on the "one-jar" jar file. It results in the dialog box shown.
Something else occasionally occurs with the list of editors when you click on "Open With". This time it is not causing any problems except loss of hair on my end. Right now I am using Oxygen Release Milestone 2 (4.7.0 M2). It happens with prior releases as well. Closing and restarting does not help any.
I have just refactored my project with many class file changes and when I start debugging the first entry class having main in eclipse, it always pops up StringBuilder with no source found and I have to do 100s of F8 to pass through that. I am not sure if that was because I made my code changes related to String or StringBuilder.
I dont know why is it not stopping at first line of my program though, I have a breakpoint there.
I tried changing JDK 1.6 from 1.7, still facing same experience.
Please suggest.
Thanks,
Narayana.V
Ensure you clear all your breakpoints. You may have one in the StringBuilder class itself.
I hope this question is appropriate for Stack Overflow; if not, I apologize. For some reason the close all functionality on my installation of eclipse stopped working. I can still close windows, but I can't close all. Neither the hot key nor the menu functionality works anymore. My theory is that it has something to do with me occasionally breaking source pages out onto other screens. Is there a way to fix this or get some sort of output out of eclipse that will provide some clues?
There are a couple of things you can try. The first step is the error log (Windows -> Show View -> Error Log).
If you can't see anything in the log, you may try to start Eclipse with java instead of javaw. Just add
-vm
...path-to-java.../java
to eclipse.ini. Maybe it prints something useful to stdout.
If that also doesn't help, try closing one window manually (for example with Ctrl+W) and then "Close All" again. Repeat until it works. That might give you a clue which window prevents Eclipse from closing everything.
If that doesn't help: You can also close windows by opening the window list (Ctrl+E). Instead of search, go down once (so the selection is in the list). You can now close windows using Delete (key repeat works but the UI lags begind).
I am running MonoDevelop 2.8 on Lion.
Today code-completion suddenly stopped working. After a while I found out it simply does not work reliably any more.
When I type a dot, usually the available methods for the object appear, but most of the time that doesn't happen any more. But when I type the object name at the beginning of a line, code completion works again for a minute or so.
I.e.
string s = "Hello world."
string t = s.
At that point the completion window should appear but doesn't. However, when instead of string t = s.etc. I start a line with "s." the code completion window appears.
string s = "Whatever"
s.
When I press the keyboard shortcut (ctrl-space) for code completion, I notice that the edit menu turns blue for a second, so apparently the actual command is received by MonoDevelop but doesn't do anything.
I updated MonoDevelop from 2.8.6 (I think) to 2.8.8 but the behaviour did not change. It wasn't like that a few days ago, it only started happening today.
Any ideas?
Update: I just tried running MonoDevelop with a newly-created account on the same computer and code-completion works. Must be something in user-specific config files. I'll see if I can hunt them all down.
Try to clean out all your pidb files. They are in your project directories as well as your home directory.
$HOME/Library/Caches/MonoDevelop-2.8/CodeCompletionData/
I have worked in project for long time but after electricity has cut off and my PC shutdown.
The code in one of my frames not shown correctly, it's showing like this :
I have GUI and its shape is fine. When I run the frame from main interface it works, but as I said the code is corrupted. I don't know why. If any one has any solution for this problem it would be much appreciated.
In your Netbeans IDE,
Open Projects window (Ctrl+1) ,select file-> right click on list select Local History-> Select Local History. It will show all your last edits. you can restore the last updates from there.
In Latest netbeans releases you can directly access this from toolbar, check the below screenshot.I took this from Netbeans 7.3