I use Windows 8 x64 and last eclipse: eclipse-java-juno-SR1.
At second monitor I move console and some android tools (logcat, devices). All worked ok. But I do not need see second monitor all time. And I switch off this monitor (by win + P). On next start I see windows from second monitor at primary monitor. Close. Open. And now see default perspective. Own perspectives, that I saved disappeared. And this repeat all time, if I disable second monitor.
Before I use eclipse-java-indigo-SR1 and do not have any problem.
Don't find solution. Now back to indigo (3.7.1).
Related
Problem
Every time I use Eclipse on my personal laptop, it constantly freezes (e.i. the process stops responding) for seemingly everything I do except for regular typing (without content assist). Any other action will cause it to freeze 7 out of 10 times, for roughly 10-20 seconds, mainly:
Any automatic proposal menus (e.g. when you type . after a variable name and a list of options appears) or manual ones (e.i. Ctrl + Space).
Any auto-import (Ctrl + Shift + O) or auto-format (Ctrl + Shift + Space)
Any context menu
Viewing JavaDoc comments
Any interaction with the project/package explorer
Any load/save operations
Any run/debug operation
Exiting the program
Every once in a while, it will not freeze, but the content assist will take a very long time to give me proposals, or the JavaDoc info will take a long time to load.
I use Eclipse on my work laptop and I do not experience any of these issues.
Things I've tried
Increase the RAM
Monitor the heap (I did not observe any correlation between heap size and freezing)
Move my workspace from my external drive to my internal drive
Run eclipse -clean
Perform a clean installation:
Delete the installation directory (%userprofile%\eclipse\java-XXXX-XX\eclipse)
Delete the .p2 directory (%userprofile%\.p2)
Download and install the latest version of Eclipse
Create a new workspace (and test it by creating a new project instead of importing old ones)
Disable the "Override high DPI scaling behavior" option (see this)
Environment
I am sure that someone is going to ask if I have a computer capable of running Eclipse. These are my laptop's specifications:
GPU : NVIDIA GeForce RTX 3070 Laptop GPU
CPU : AMD Ryzen 9 5900HS with Radeon Graphics
Memory: 16 GB RAM (15.41 GB RAM usable)
It's a ROG Zephyrus G15 (Model: GA503QR_GA503QR). I previously owned a G14 and had the same issue.
Observations
I notice that often when this happens explorer.exe also stops responding. I can still use other applications like Google Chrome, but I have to wait for Eclipse to respond before Windows Explorer starts responding.
Question
What are the potential causes of the described behaviors, and remedies thereof?
I'm always working with multiple nodejs projects, and every time I debug a new terminal is opened so I'm constantly getting lost on which terminal corresponds to each debug session.
Is there some way to do something like double clicking the debug session in the call stack and open the terminal it corresponds? Any insight would be greatly appreciated.
Thanks.
Based on my personal experience, looking at all the logs in one terminal makes it more confusing.
I have a better alternative for you, so let say you are debugging A and B projects.
Open A project in one window of VS code and use an integrated terminal
Open B project in another window of VS and use integrated terminal
and so on...
(To open the integrated terminal, Mac: Cmd + j and for Windows: Ctrl+` )
Windows:
Ctrl + Shift + P
Mac:
Cmd + Shift + p
And running those hotkeys type: Terminal: Rename, now you can change the terminal title
You could also add a keyboard shortcut for this command: workbench.action.terminal.rename
in addition to the answers, my approach is isolate the VS by opening different windows for different sessions, and keep the 2 windows on 2 different monitors, for that you need an extra monitor.
when i had 1 monitor, identifying which window corresponded to which was a time waste task and more of distraction. now attaching extra monitor to laptop has saved me a ton of time, organizing windows and switching between became seamless and of course most importantly, productivity and speed increased around 33%.
When I open a pydev console, it takes several seconds before I get a cursor. I have a single file "Hello World" sort of project. There are no large variables to show.
My installation used Kepler-CDT, and I then installed PyDev (Latest, version 3.6.0)
I right select the console icon, select New PyDev Console, and then the console selection dialog appears. I select "Python console" (OK).
"Create Interactive Console" shows in the eclipse progress bar. Eventually, IPython starts, and after 20 seconds or so, I get a >>> prompt.
If I press enter at the prompt, another prompt appears as expected, but it usually take 4 or 5 seconds.
Some suggestions I have seen talk about firewall issues, how would I go about checking this?
How do I debug this problem?
What's your OS? From what you're saying, the issue really 'appears' to be either some network misconfiguration or possibly some firewall/antivirus making things slower (you can try disabling those to test if things go faster). As for a network misconfiguration, you can try checking your hosts file to see if things are correct there (I've had reports where there were other things, but these are the most common -- for other situations it may be more difficult to diagnose as usually each particular case is something different).
Upon checking Task Manager (Windows 7), I have approximately 60 instances of javaw.exe running, ranging from approx. 1,000K - 450,000K.
I am currently working on a large project, developing some software using Eclipse Helios.
Can somebody explain why this is happening?
Lots of possible reasons for this, but in my experience the most likely is that instances of your app that you are starting to test or debug are staying around after you think they are gone.
If you don't explicitly stop the previous instance, and click the "Run As" (Green Arrow) button again, the previous instance will just keep running in the background. In the console tab, there is a drop down which will show all running instances. You need to click the red box on each of these to kill the process.
I think it's a bug in Eclipse. When you stop the console - clicking the big red button - the javaw.exe process carries on running.
You solve it by opening task manager, identifying the javaw.exe process that isn't for Eclipse (go to show columns and show "command line") and then right click: end task
I'm using Eclipse + pydev plugin as the development environment. In fact my application needs a big console area and I usually resize the console and minimize it, so that whenever I run the application, it automatically shows up.
But when I minimize the console view or detach it or mark it as Fast View, the toolbar for controlling the running process and locking the scroll disappears.
Can I have both minimize functionality and Process control toolbar ?
Eclipse : Galileo Build id: 20090619-0625
Pydev : 1.5.3
Right now, in Eclipse/PyDev, you can't have the toolbar when it's minimized (you have to open it to access it), but most of what you need should be available through shortcuts (some may need focus on a PyDev editor):
Terminate current process: Ctrl+F2
Terminate all processes: Ctrl+Alt+F9
Terminate / relaunch last launched process: Ctrl+Shift+F9
To launch the currently open editor: F9
To relaunch the last launch (provided you followed the steps at: http://pydev.org/manual_101_run.html): Ctrl+F11
To debug the last launch: F11
To show the console view: Alt+Shift+Q, C
And if you want, you should be able to configure those in the keybindings (Ctrl+Shift+L twice to open the preferences page to do so).
I used eclipse with pydev and it drove me nuts. I use Netbeans 6.8 right now which came bundled with its own python plugin that is a lot better. Especially when it comes to debugging.