Page 1 of 1

Java 7 messing with my Salem

PostPosted: Sun Sep 02, 2012 9:49 am
by Arurra
Hey,

So today I finally updated to Java 7. And since i have frozen when:
1. Shift clicking to fill smelter with coal.
2. Porting to Boston.
3. Shift clicking to move stuff from inventory to box.

Running Java 6 I have never had any problem, but after updating to Java7 I have crashed 5 times in 2 hours.
Anyone have any ideas of how I can fix it? or are the Devs. planing on a Salem hotfix or something to make a smooth out the problem?

I have heard others on the IRC having problems - which is why I really didn't want to update - but because other programs need the update I had to too update :(

Any help would be appreciated.

Btw I'm using Enders client - I don't know if this has any association with the freezes?

Re: Java 7 messing with my Salem

PostPosted: Sun Sep 02, 2012 10:32 am
by dullahx
uninstall java 7

Re: Java 7 messing with my Salem

PostPosted: Sun Sep 02, 2012 10:38 am
by Tonkyhonk
basically, you should try on default client and see if it crashes like it does with enders.
if it doesnt crash with the default client, you should ask in ender's thread.
if it crashes with the default as well, then loftar will look into it, no doubt.

Re: Java 7 messing with my Salem

PostPosted: Sun Sep 02, 2012 11:25 am
by Droj
Remove Java 7, put 6 back on. Not had a crash since

Re: Java 7 messing with my Salem

PostPosted: Sun Sep 02, 2012 12:25 pm
by Jacra
From my playing around it seems to be Java 7 and not Ender or such. Not sure if others can confirm this but according to task manager on my end there are when it happens several instances of javaw application open, each around 480 or such MB. Which basically might be a memory leak that with instances adds up and then freezes/crashs?

Re: Java 7 messing with my Salem

PostPosted: Sun Sep 02, 2012 3:49 pm
by MagicManICT
No, it's definitely Ender's that crashes in Java 7 if I understand correctly. I'm not sure if he's pinpointed the bug and is waiting on Oracle to fix it, if he's still searching for it in his code, or it's a conflict with some of the core source code.

It is possible to run both versions, but it is difficult to set up and prone to failure if not done correctly.

There should be one instance of javaw.exe open for each instance of a Java applet running. If you have more than one open, then there could be problems if you haven't launched any other applets.