+- Forums - Open Redstone Engineers (https://forum.openredstone.org)
+-- Forum: Off-Topic (https://forum.openredstone.org/forum-4.html)
+--- Forum: Off-Topic Discussion (https://forum.openredstone.org/forum-5.html)
+--- Thread: Suggesting to reboot the modded server. (/thread-4528.html)
RE: Suggesting to reboot the modded server. - Chibill - 10-21-2014
Some how it's only getting about 900 mb of ram.
RE: Suggesting to reboot the modded server. - PhysoniumI - 10-21-2014
Yeah. Give it more RAM and pregen.
You're giving it a max of up to 1037959168 bytes (989 MB), maybe due to your system being too heavily used RAM wise. I don't know without more information.
RE: Suggesting to reboot the modded server. - Chibill - 10-21-2014
I will look into the At launcher on my end and try fixing it.
RE: Suggesting to reboot the modded server. - PabloDons - 10-21-2014
it's not the ram that is the problem, that is a gigabyte of ram. there is actually only 200-300 mb ram being used anyway. also I even tried with more ram than my computer has.
Here's a crash report with more memory than I could possibly imagine
RE: Suggesting to reboot the modded server. - Chibill - 10-21-2014
I will debug when I get home.
RE: Suggesting to reboot the modded server. - TSO - 10-22-2014
Launch minecraft verbosely from the command line and pipe that into a text document. It will make the error much easier to find because it will be in the last line and the command line will tell you what went wrong. (Works every time for me and my father at least.)
Ooooh! IIRC, you can compile java into full machine code with GCC, and you can compile it into C code so that people can actually figure what what the hell went wrong. Use the -O3 -march=normal -mtune=normal extensions to optimize to your system. (Note: this will take forever to compile)
RE: Suggesting to reboot the modded server. - Chibill - 10-22-2014
I have no idea whats the problem with the AT launcher it works on my end.
RE: Suggesting to reboot the modded server. - PabloDons - 10-22-2014
(10-22-2014, 07:25 AM)TSO Wrote: Launch minecraft verbosely from the command line and pipe that into a text document. It will make the error much easier to find because it will be in the last line and the command line will tell you what went wrong. (Works every time for me and my father at least.)1. I don't know what any of that means
Ooooh! IIRC, you can compile java into full machine code with GCC, and you can compile it into C code so that people can actually figure what what the hell went wrong. Use the -O3 -march=normal -mtune=normal extensions to optimize to your system. (Note: this will take forever to compile)
2. I don't even... 0.o
RE: Suggesting to reboot the modded server. - TSO - 10-23-2014
(warning:post not edited except where it is extremely important. Read all instructions before actually trying to fix minecraft.)
Prerequisites: if you have less than 2 or 3 GB of RAM, allocate less than 500MB to minecraft and see if that fixes the problem. If it does, slowly raise the amount until you get the error again. Your operating system may be refusing to allocate 1GB of space because the process table divides the memory into 64KB blocks and distributes them somewhat equally between programs. This would lead to the program trying to access memory that belongs to another process because it thinks it has 1GB, and then the operating system denies the memory access and forcibly kills the program.
If that doesn't work:
First part:
You will need either Linux, a Unix, or Cygwin. (Cygwin is a Linux shell for Windows, the command prompt might be able to do this, but I doubt it.)
If you don't have these, download Cygwin from here. I will help you from there. If you are unsure if you have these, verify that you aren't running windows. That's your answer.
Step 1:
If you have a *nix system, ignore this step.
You need to go to your minecraft folder in Windows Explorer and knock that space out of the "minecraft launcher" folder. Then enter the folder and knock the space out of Minecraft Launcher.exe (this has no effect on windows, but linux systems don't allow spaces in file names, so cygwin won't be able to get to the directory. If any of the folders this folder's path also have spaces, they will need to be concatenated as well.)
Step 2:
Launch the terminal and cd to your minecraft directory.
Step3:
type "ls" without quotes, this lists all files in the directory. Verify that there isn't a space in MinecraftLauncher.exe
Step4:
a.) verify there isn't a text.txt file, if for some bizzare reason there is, choose a different name for part c
b.) type the following line
MincraftLauncher.exe --help
This gives you a list of extensions for the minecraft launcher (notice how "--help" is one of them?) type them in with their syntax for extra magic.
b.) type the following line
./MinecraftLauncher.exe [operation] > text.txt
This will create a new file in the directory called text.txt and cause a launch of minecraft, every process call and a bunch of useful debugging stuff gets written to the command line screen. The operation field is optional, but if filled, minecraft will execute either just the requested operation or it will launch with the operation. (for example --help didn't launch minecraft, just the help). The pipe "> text.txt" wrights this all to text.txt. Because of this routing, you won't actually see what happens.
Step5: Once your launcher has failed, wait a couple of seconds (to make sure it finishes wrighting), then either go back to windows explorer and open text.txt in notepad, or do the following (note, if you don't know how to use vim, do not try this. Trust me, you will not figure it out on your own.)
Type, without quotes "vim text.txt"
This opens the text file in vim. What you see is everything that the launcher requested, and it's completion status, followed by reports of unimportant details. For example, in mine, the script that verifies my account fails because I'm using cracked minecraft.
Now, if the actual exe failed on launch, you should actually get a report in the shell saying exactly why it failed and at what line it failed at in the java script that failed. This failure is probably going to be caused by the operating system refusing to allocate memory or detecting a memory violation from what it sounds like.
Okay, If you get away without any reports, and it still doesn't work, you'll need the Java process report thing again, but you will also know from your text file exactly which scripts are still working properly. Between the two, there is no way you will not be able to find the error. If you are unsure what the shell error means, these are all well documented on the interwebz.
The second part:
GCC is the GNU Compiler Collection. I think it has the ability to compile java code into machine code in order to speed up the program by not having it compile in runtime. -O3 is the highest level of general optimization. -mtune=native optimizes for the instruction set quirks of the computer doing the compile, and -march=normal optimizes for the architecture of the computer doing the compile.
RE: Suggesting to reboot the modded server. - Chibill - 10-23-2014
I think you can do this in windows with out cigwin using >>