Forums

•´¯`•-> Silent Skills <-•´¯`•

Quick find code: 93-94-688-63155221

The contents of this message have been hidden.

03-Feb-2012 22:38:18

[#N3N19FHAH]

[#N3N19FHAH]

Posts: 691 Steel Posts by user Forum Profile RuneMetrics Profile
(Forum Mods, Please do not delete these posts and hide them.. It is a solemn purpose to help my fellow clan-mates with issues they may have As Linux users.)
Hello everyone, If there are Linux users in this clan and are having trouble with runescape game crashes and load up crashes.. I have fixed the problem. In the next few posts i will be explaining what happened and what i done to repair the flaw in jagex's last update.
My Java Specs I am using are:
openjdk:
java version "1.6.0_23"
OpenJDK Runtime Environment (IcedTea6 1.11pre) (6b23~pre11-0ubuntu.1.6.0-ls)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
sun/oracle:
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode

I have been playing Runescape for a long time now on Debian/KDE/XFCE/Gnome LINUX. Using the FireFox browser and had installed Sun-Java6-1.6.0_30 was running fine and then....
Feb 1st, 2012 Jagex Updates..
(First load up since the update)
"Error_game_crash - A problem has occurred while running the game.
This game has encountered a problem and cannot continue running.
We strive for our games to work on as many computers as possible and to be free of bugs.
If you are able to reproduce this problem (i.e. it always occurs when you do a certain thing), then please submit a bug report via our website, and we will try to fix it as soon as possible.
If problems persist, please refer to the Technical FAQs, which can be found in the Customer Support section of our website."

04-Feb-2012 03:45:49 - Last edited on 04-Feb-2012 04:09:05 by [#N3N19FHAH]

[#N3N19FHAH]

[#N3N19FHAH]

Posts: 691 Steel Posts by user Forum Profile RuneMetrics Profile
What happened???? Did a runescapes "update" destroy the ability of LINUX users to play???
A few of my friends and I on Runescape>Forums>Technical Support>Discussion-Linux Thread had all worked together many hours (27 hours total) to band together as well with *Mod Dowd* to come up with a reason for this inflicting problem. We have come to a conclusion to write a log of all our steps but however if i were to type it all here it would take up 7 pages. But i have summed it all up in a few posts. We all ahve come to a conclusion that where the problem was, is in a hidden file deep in the core of the hard drive that my eyes have allowed me to see through the comands and encoding of JavaScript Development.

You can provide arguments for applets by writing the 'deployment.properties' file.
> Sure you actually turned off the JIT?
Yes.
>What is your error?
Stack overflow. Stack trace shows a huge list of alternating repeated calls to two methods. Infinite recursion eventually overflowing the stack ? Hmm.
>The one I started getting today is.
>Exception Type: EXC_BAD_ACCESS (SIGBUS)
>Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000018
>Crashed Thread: 14 Java: CompilerThread0
Looks like a NULL pointer exception in the compiler. It is logical that you won't see this in interpreted code.

04-Feb-2012 03:53:28

[#N3N19FHAH]

[#N3N19FHAH]

Posts: 691 Steel Posts by user Forum Profile RuneMetrics Profile
In my linux this file is in ~/opt/java/jre/bin folder. But only allowed to be access via Root. And in text form. To enter Root.. Open a terminal and type: Su. Then enter Root ********.
Its contents look like this:
#deployment.properties
#Wed Feb 01 17:23:50 CET 2012
deployment.version=6.0
deployment.capture.mime.types=true
deployment.browser.path=/usr/bin/firefox
#Java Deployment jre's
#Wed Feb 01 17:23:50 CET 2012
deployment.javaws.jre.0.registered=true
deployment.javaws.jre.0.platform=1.7
deployment.javaws.jre.0.osname=Linux
deployment.javaws.jre.0.path=/opt/java/jre/bin/java
deployment.javaws.jre.0.product=1.7.0_02
deployment.javaws.jre.0.osarch=i386
deployment.javaws.jre.0.location=http\://java.sun.***/products/autodl/j2se
deployment.javaws.jre.0.enabled=true
deployment.javaws.jre.0.args=-Xms512m -Xmx1024m
Even after that we could not get it fixed. So then I had a theory and *Mod Dowd* tested it. WHen jagex adds updates in their coding and source, then must have added a code by mistake to overflow the jagex>Sun-Java cache file. (Another file hidden in the depths of linux that is almost impossible to break into even as the Root user of the system. Yet did we know that my theory was correct and did fix the issue and got many people online using linux.

04-Feb-2012 03:59:54

[#N3N19FHAH]

[#N3N19FHAH]

Posts: 691 Steel Posts by user Forum Profile RuneMetrics Profile
It was the stack size (duh). The latest update must have added code that would overflow the stack if left at whatever my default value was (probably 512k). I gave it 1MB and Runescape is running happily again on JRE1.6.0_anything and with OpenGL !
So for all of you who still had the Error_game_crash message, simply increasing the JVM stacksize (-*ss1m) is definitely worth a try !
(The censor filter swallowed my command line flag. Replace the * above by the capital letter x)
You have to pass the parameter to the JVM your browser is using to run the RS applet.
Open the file "deployment.properties" (located in ~/.java/deployment) with your preferred text editor. In there you will find, amongst others, a line called
deployment.javaws.jre.0.args=
You add the flag after the equal sign, ie:
deployment.javaws.jre.0.args=-Xss1m
Note that there may be more than one, with different indices (0, 1, 2, etc) if you have more than one JRE version installed. You must add the flag to the right version (or to all of them, if you dont know the right one, it shouldn't do any harm).
Then restart firefox and try to run the game.
it's a per-user setting. In your home directory there should be a directory called ".java" (it's hidden). In there will be another directory called "deployment". Finally in there you will find the "deployment.properties" file.
f you're having trouble finding the file, you can also use the Java control panel:
run the executable: /usr/java/jre1.6.0_30/bin/ControlPanel
Select the "Java" tab and click "View". In the list choose the JRE your browser is using (there's probably only going to be one in your case) and put the -Xss1m flag into the "Runtime parameters" field. Press OK and again OK to close the control panel. It basically does the same changes as the manual ones I described above.
OK, Its solved finally ! Relief... Goodluck on the repair of the Jagex Update FLaw on your Linux OS. if you have any questions just ask me :)

04-Feb-2012 04:01:34

Quick find code: 93-94-688-63155221 Back to Top