This isn't coding related, I hope that's fine. I've been trying to run a modpack through techniclauncher, but I can't get the launcher to even open.
If I have java 64bit installed, anything I open that uses java just stays in the taskbar/task manager for about 3 seconds, then closes with no error message. 32 bit java works, but I need 64bit so I can dedicate more than 1GB of ram to a modpack.
I am on Windows 10 x64 build 1903, my java version is JRE 8u231 but no matter which version of java I install the problem persists.
Things I've tried:
uninstalling/reinstalling
Using revouninstaller from Britec's tutorial
Installing an old version of java (Java 6 had the same problem, same with older versions of java 8)
jarfix
updating graphics drivers (gtx 1070 currently on 441.41)
I have no idea what caused it; it worked fine a few months ago and when I tried to launch a modpack yesterday the launcher wouldn't start. Even the java control panel doesn't work. Any help would be appreciated, thanks in advance!
[EDIT: screenshots of event viewer]
https://gyazo.com/70c9b5599fe3331e927171a6ac279e25
https://gyazo.com/1786c8011182933e3671481966394507
https://gyazo.com/da029d89cfdf0da6a3af4cb5a4c9b083
https://gyazo.com/a0a377129d51ee7b51a4b2aefce8723f
https://gyazo.com/4ad84929c5f1c0e93834289616f4afb2
This all happened at about the same time when I tried to open the Java control panel
The error message seems to indicate the crash has something to do with graphics / Direct3D. Finding the root cause might be difficult, but one thing to try would be updating your graphics drivers.
Another thing to try would be to disable Java's graphics hardware acceleration. The System Properties for Java 2D Technology page has instructions on how to do this. Under Windows, to configure globally for all launched Java applications, set the environment variable _JAVA_OPTIONS to -Dsun.java2d.d3d=false to disable Direct3D acceleration.
I'm using the eclipse neon IDE and I put it on the path: /opt/eclipse/eclipse and i am using Ubuntu 16.04 and Java 8. The problem is that when I write in the eclipse editor, this is going too slow. For example, I just typed and in the editor it still does not end.
How can I solve it?
Thx!
Try Netbeans, or IntelliJ IDEA.
A quick browse over the Interwebs shows that quite a lot of people are complaining about Eclipse slowness. Some have every manner of trick and configuration change to help speed it up. OK, you can put yourself thru all that hassle if you want, or, you can just switch to something that already works fine out of the box.
I had Eclipse Oxygen for PHP running on a CentOS 7 VM with 2G allocated RAM. I admit, that's pretty low memory, but that's the way it has to be right now. Eclipse ran so slowly, I finally gave up and killed the process from the command line.
I installed the latest Netbeans 8.2, and it not only installed more cleanly (no Java error messages, and it put an icon on the desktop), it ran PERFECTLY without changing a thing!
I eventually changed a couple of parameters, but the point is, I didn't need to change a thing to get decent performance. Even on a low-ram system, it ran plenty fast enough.
Don't blame the hardware. Not everybody has the money to buy the latest and greatest and fastest machines available, and software developers should not expect it. With some exceptions, if your application can not run adequately on 2G of ram, you are doing something wrong.
The Eclipse developers are doing something terribly wrong.
I had faced a similar issue with eclipse oxygen.
After a some research over different forums I found the following solution.
Step 1 : Open eclipse.ini file. If you find difficulty in locating the file, see this question Where's the location of the eclipse.ini file?
Step 2 : In eclipse.ini search for below 2 variables
-Xms
-Xmx
Xms indicates minimum ram that should be allocated to eclipse.
Xmx indicates maximum ram that should be allocated to eclipse.
Step 3 :Increment both the values. You can set the value as per your choice. Below is my preference.
-Xms512m
-Xmx2048m
Here
m indicates megabytes, if you don't specify m it will consider bytes by default.
The easiest thing to do would be to re-install eclipse, and if that does not work you could try to download an older version of eclipse. It could also be slow because your computer is slow.
I've recently installed Ubuntu (16.04) I've noticed that after the first build of a project on Eclipse (I've tried this with Luna and Mars) that the editor starts to run slow. There is a noticeable lag when typing and selecting text etc. It doesn't make it unusable, but it is fairly irritating. I've done the following to try and fix this, but to no avail:
allocate more memory in eclipse.ini
set the environment variable $SWT_GTK3=0 (as I found something that said there may be a gtk3 bug in 16.04.
update graphics drivers
At this point I'm really not sure what else to do. It seems to run well at first, but after that first build (Java) it just dies a bit. Any suggestions on what I could do to try and fix this would be much appreciated!
It's the first time I've used Eclipse with Ubuntu, as normally I'm on a Windows machine, so I'm not sure if maybe I've just not set something up properly.
add the below lines into the eclipse.ini file:
--launcher.GTK_version
2
before the line:
--launcher.appendVmargs
I am on Ubuntu 16.04 with NetBeans 8.1 - fresh install provided by Ubuntu SW center + OpenJDK - default with Ubuntu.
When I follow the video manual on codename one web site: https://www.codenameone.com/download.html
I do not get option to install codename one plugin.
To be precise, there is not a single available plugin listed.
In Windows 7 this works fine however.
I don't even know, who should I attribute this problem to:
Ubuntu 16.04 ? - which sucks and behaves weird compared to earlier Ubuntu versions (now for instance does not close the open and frozen NetBeans - had to kill -9 it)
Net Beans 8.1 ? which runs just fine with Win7
codename one ? Which I rather doubt :)
or even me ? :)
Please give me any hints, if anyone ran into similar troubles, how do I fix it ?
We need to the official Java 8 JDK for install since we need access to Java FX for things such as web browser/media support. If OpenJDK will ever work with Java FX properly then it should work fine with Codename One.
Here is the solution:
Part of the story is, that you should use original JDK from Oracle, not the pre-installed OpenJDK. Similarly, Android Studio will complain about incompatible JDK.
But secondly ! Using the NetBeans installation provided by Ubuntu SW center results in incomplete, or not updatable version. Simply you get no available plugins listed. Only those pre-installed. Moreover, this IDE freezes much too often. What the heck !?
Instead download and install NetBeans from their site:
I went for the full version.
For this and many other reasons I think I am done with Ubuntu 16.04
Every day it convinces me it does not YET deserve to occupy my disk space. I will probably step back to 14.04 LTS, until 16.04 LTS it reaches some mature state.
I am using eclipse 3.5 (cocoa build) on Macos 10.5 with Java 1.5.0.19.
I just have 3 java files opened
1 files ~ 2000 lines
the other 2 are ~ 700 lines.
But when I switch from 1 file tab to another, eclipse takes a long time (~ 20 seconds) to switch to another tab.
I have already change the eclipse.ini to
more eclipse.ini
-startup
../../../plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar
--launcher.library
../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx_1.0.0.v20090519
-product
org.eclipse.epp.package.jee.product
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vmargs
-Dosgi.requiredJavaVersion=1.5
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
-XX:MaxPermSize=512m
-Xms128m
-Xmx1024m
-Xdock:icon=../Resources/Eclipse.icns
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
Is there any way to make eclipse 3.5 more speedy?
Thank you.
I switched this line in the eclipse.ini file (found inside the eclipse application package):
-Dosgi.requiredJavaVersion=1.5
to
-Dosgi.requiredJavaVersion=1.6
and tab switching was speedy again.
Go with the 32-bit Cocoa release. The 64-bit won't help IMHO. It really works great on my 2.4 GHz MBP. I usually have about 30 files open, some fairly large, never experienced what you describe.
Try to get a new plain-vanilla 32-bit Cocoa distro, don't modify anything and check if there's an issue. It could be a rogue plugin, too. Do you have any installed?
Check you heap status. Open the Eclipse preferences, in the very first preferences page there's a "show heap status" option. You might be running low on memory. Check the swap status of your machine using the activity monitor - if it swaps a lot I'd recommend shutting down other applications. In general, I recommend 4 GB RAM for development machines.
I know this is kind of late to the game, but I found that changing the permissions to ~workspace.metadata.plugins\org.eclipse.e4.workbench to deny myself access stopped the slow-down issue.
Seems that Eclipse (4.2.0) writes out a corrupt settings file every so often, and when it's loaded in at startup again it slows everything down as it's constantly throwing errors internally. Changing the security on that directory so that Eclipse can't write to it is a kind of "fix"! It does mean that each time Eclipse is started it's back to its default settings, but if speed is more important, I think it's a worthwhile sacrifice.
There are now patches for Juno to begin addressing this issue. See comment #212 on bug 385272 for information on how to update your installation. If you wait a little longer you should find these fixes in the Kepler milestone on 12/21/2012.
(I believe the other suggestions posted here, e.g. increasing memory or tweeking various startup params or prefs might have some positive effect on performance, but the underlying problem is threads run amok as described in the bug report.)
This might be the bug that was referred to. https://bugs.eclipse.org/bugs/show_bug.cgi?id=282229
switching to 1.6 really helps.
This is the link to locate eclipse.ini file for mac
http://wiki.eclipse.org/Eclipse.ini
This eclipse bug report is spot-on with the behavior you describe. (I had the same experience using a new Juno installation on a beefy XP machine.)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=385272
The most useful part of the bug report was in comment 29, which suggests creating a new workspace. The easiest way to do this is:
1) exit eclipse
2) rename .../path/to/workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
(e.g., append ".old")
3) start eclipse
I believe changing -Dosgi.requiredJavaVersion=1.5 to 1.6 may help only incidentally, if at all.
Increase the memory limits in eclipse.ini seems to have fixed this for me - not sure if it will stay fixed though
FROM:
-vmargs
-Xms40m
-Xmx512m
TO
-vmargs
-XX:MaxPermSize=512m
-Xms256m
-Xmx784m
ALSO - if you came from aptana3 and imported your project - You need to do this
Click Project Properties
Go to "Builders"
Make sure there are no "Missing Builders" If there are, uncheck them - I had two left over from aptana when I imported my project (com.aptana.ide.core.unifiedBuilder AND com.aptana.editor.php.aptanaPhpBuilder)
---- UPDATE ----
It was fixed - but not for the reasons I thought. My SVN was no longer recognized by eclipse. As soon as I hit 'share with team' and reconnected it the tab-switching issues reappeared. I'm going to try and figure out if It's an svnKit vs JavaHL problem - I'm not sure which connector I picked when I setup eclipse this time.
If you want confirm this is your issue trying disconnecting from the SVN (Team->disconnect) and restarting eclipse
This is an known issue.
Since you are using JDK1.5, you can try the Carbon variant.
I experience the same issue using OS X 10.5.7 and Eclipse 3.5.2 on a fairly low end machine (early 2006 iMac with 1.5GB). Right after I start my machine however, everything is really snappy. I can even launch JBoss AS and there is still no slow-down. I monitor "Swap used" in activity monitor, and it stays at 0 bytes swap used.
Then, I launch something else, like iTunes and mail or switching to another account.
Things become slow then, which is expected, and I see "Swap used" increasing. Eclipse slows down to a crawl, and working with it is near to impossible.
Then I logout the other account, close down all other apps that I opened, so the state of my machine is basically the same again as when it was still fast. BUT... it stays dog slow! Even though I closed all the other apps, "Swap used" in activity monitor only decreases a little (from ~1.2GB to ~700MB). Just switching tabs between 2 very simple Java files takes up to 20 seconds, meanwhile I see in activity monitor that the CPU usage goes up to a solid 100%.
There definitely is something strange going on here. This does not seem like normal behavior. It is as-if Mac OS X goes into a 'slow mode' when I demand too much resources from it, but when the resources are there again it fails to recover.
Highly annoying!
If I reset the machine and open the exact same working set again (Eclipse with the same 2 files open, JBoss AS started in debug mode, Safari with 1 window) everything is really fast again.
I can now more or less confirm that the problem is really with Eclipse 3.5.
I've run Eclipse on a much more powerful Mac, a 27" core I7, 2.93Ghz with 8GB ram and a SSD running OS X 10.6.4. Initially this was extremely smooth and snappy, but after an up time of a dozen hours or so, Eclipse suddenly began to slow-down again. I had very little to almost nothing running in the background. Just Eclipse (32 bits, given it 1.5GB memory), JBoss AS and Safari.
A simple tab switch would take a few seconds and meanwhile I noticed the CPU load on one core going to 100%. The same happened with switching perspectives and various other operations.
When I restarted only Eclipse, everything was completely fast again. This happened a couple of times.
For me the issue was the SVNKit connection integration to the Juno version of Eclipse. I am doing Android Development using the Juno version of Eclipse and when I turned on the SVNKit Team Integration I got the following issues described:
Very slow switching between code files in the Eclipse IDE.
Extra large gap and space in the tool bar between the print and Android SDK Manager icons.
For me... I turned off the following settings under Window->Preferences->Team->SVN under the View Settings... there was a setting for "Show synchronize info incrementally"... I turned that off and the switching between files improved.... but there is still a delay versus NOT having SVN connected.
Without SVN connected... the switching between files is normal.
I had Java 1.6 in the Eclipse.ini
I did not change the settings for memory.
TL;DR for the bug thread:
http://wiki.eclipse.org/Platform_UI/Juno_Performance_Investigation#Resolution
Worked for me.
The original problem of slow switching between tabs has reappeared in Eclipse Neon (4.6.2 only?) using the Dark theme.
Solution: disable themed scrollbars in e4-dark_win.css (bottom of file):
StyledText {
swt-scrollbar-themed: false;
[...]