Crash on Linux Mint 17

[Eobersig 1,005]

Crash while standing in my workshop imping. Now with Oracle Java.

 

hs_err_pid at http://pastebin.com/JnjN1fZT

[xzea 20]

Why are you using x86 Linux version on an x86_64? It would be better if you used the 64-bit version of linux mint. I run the game fine on Linux Mint 17 using OpenJDK but with 64-bit version. Maybe the issue has to do with a bug that only effects the 32-bit JRE.

[Eobersig 1,005]

and another crash, while grooming horses.

 

hs_err_pid at http://pastebin.com/DDSVXV23

 

[Eobersig 1,005]

Why are you using x86 Linux version on an x86_64? It would be better if you used the 64-bit version of linux mint. I run the game fine on Linux Mint 17 using OpenJDK but with 64-bit version. Maybe the issue has to do with a bug that only effects the 32-bit JRE.

 

Do I have a 64-bit hardware architecture? You may laugh, but I really don't know ...

[xzea 20]

Do I have a 64-bit hardware architecture? You may laugh, but I really don't know ...

 

Yeah the log says you do "AMD Athlon 64 X2 Dual Core Processor" is a x86_64, so better to use the 64-bit version.

[Twinsen 350]

Try deleting the contents of packs directory.

[Eobersig 1,005]

Thanks all, I switched to Mint 64-bit now. Let's see if that helps.

[Eobersig 1,005]

Just a status report: 2 days now on Linux 64-bit, Java 64-bit. No crashes in these 2 days, sadly also a very noticeable drop in performance.

 

Had frames limited to 30 fps on 32-bit, was nice and kept the fan noise down. Now with limiter at 30 fps it's more fan noise - and over a play session performance gradually degrades to 20 fps.

 

Thus a gain in stability and a loss in performance. Not sure yet what to do.

[drinkie 17]

regarding a loss in performance :

run "top" in a terminal to see if java is taking 100% cpu or close to it, and also to see what else is taking cpu.

Also, run this command to see what GLX implementation you have :

xdpyinfo | grep -i glx

[Eobersig 1,005]

Java is taking anywhere between 70 and 150% of CPU, mostly around 90%, the other 10% usually go to Xorg and Cinnamon.

 

xdpyinfo | grep -i glx outputs 2 lines:

GLX

NV-GLX

 

Note it's not only Wurm where performance is worse on 64-bit. I wonder whether 64-bit Linux and 64-bit Java generally need more power/memory than the 32-bit versions.

 

As for the crashes: no crash on the 3rd day as well.

[drinkie 17]

The NV-GLX shows that you are using nvidia's drivers, which is good.
In general, performance should not be worse when in 64 bit mode.
You might try playing around with the graphics settings.
Also, check that you are not running into swap
(top will show amount of swap used, and this should not be
large or growing).

As a data point, I am using a 4 year old intel i7 CPU @3.2 Ghz
(http://cpuboss.com/cpu/Intel-Core-i7-960)
and getting 60 FPS with java using 90% cpu.
When I limit FPS to 30, java uses only 40% cpu.
 

[Eobersig 1,005]

Thanks, drinkie.

 

Here's a screenshot with the output from the Linux top terminal command:

 

 

 

 

 

 

100% CPU, free memory, 20 fps. With same settings on 32-bit Linux and 32-bit Java I'd get 30 fps with less CPU load (judging from the fan noise).

 

[drinkie 17]

Sorry, I dont know why your system degraded when you upgraded java.

Your "top" output doesnt show anything particularly wrong.

The only thing I can think to suggest is to try lowering some graphics settings.