**Let me first point out that even though it seems like this was caused by and occurred on a modded minecraft client, (while it first appeared on a modded client) I did indeed clear everything and force update, and this problem was still visible. I even re-installed minecraft, removing the .minecraft folder and everything, and this problem still remains. (It's gotten to a point where I've even copy and pasted a fellow mate's .jar and it still occurs.**
Summary:
It was a usual day of minecraft on my computer this morning. As the day went on, I ended up adding/removing various mods when suddenly, the options tab visible in the main menu and in-game refused to open, and would crash the client once clicked. Whenever I click on the options tab, whether it be in-game or when I'm on the main menu, my client immediately crashes, showing the dirt background that appears on all clients, and [thankfully] comes up with a crash report. I've tried throwing my options.txt and .bin into the trash, and force updating in every possible way, (I even re-installed the client) yet it still crashes upon clicking on the options tab. And yes, my client was completely un-modded when this occurred. Regardless with it modded or not, it still crashes. I'm thinking this might be an issue with my computer system, but then again, I have no idea. As displayed below, my java version is updated to the highest possible on my computer (still valid with mc, as it's above java 5).
My complete crash report is viewable below and can be downloaded.
And yes, I have already submitted this issue to the "official bug reporting website" monitored by the devs. They said it was a duplicate of other problems, unfortunately linking me to other solutions that consisted of "just force update your client," which, as stated above, I have already done.
System Specifications:
-Year = Not sure what year this computer is from, as it's from a friend's computer lab, but it's definitely over 7 years old. (Just for clarification, this computer is definitely not too old to run minecraft, as it was running it just fine earlier this morning, and has been for as long as beta was introduced.
-Type = Mac Tower (Not sold anymore, but similar to that of a Mac pro). Basically a Monitor hooked up to a tower or computer unit.
-OSX Version = 10.6.8
-Java Version = 1.6.0 (aka. Java 6). Yes, I'm running Snow Lepoard, not Lion, as Java 7 doesn't support any operating system lower than Lion.
I can attempt to provide more information about my mac if needed, but I don't think my system is the issue, as once again this was perfectly fine this morning. I'm guessing it's a problem with my .minecraft folder. What seems interesting is the fact that force updating won't include all of the necessary files in a default un-modded client (just to name some, the sound files weren't all included. I had to install them manually) which is why i'm assuming the problem is not with my system.
Any and all help is appreciated. Thank you for your time.
Hmm... Indeed it still occurs. Thank you for the attempt though.
Analyzing the crash report, it seems that I am missing a class file, most likely indicating that my .jar is corrupt, so you're on the right track. The issue is probably along the lines of my .jar.
Like i said at the top, (even though that might work) it was still working perfectly fine this morning. Unless my computer "cracked," I don't see a reason why it wouldn't work now...
EDIT: Thinking back to what I was doing, since I was force-updating my jar dozens of times due to mods, something in my jar must have screwed up, meaning again, my .jar might be corrupt. Something in my computer might be blocking parts of the jar during the force update... I'll check on my firewall, etc.
Summary:
It was a usual day of minecraft on my computer this morning. As the day went on, I ended up adding/removing various mods when suddenly, the options tab visible in the main menu and in-game refused to open, and would crash the client once clicked. Whenever I click on the options tab, whether it be in-game or when I'm on the main menu, my client immediately crashes, showing the dirt background that appears on all clients, and [thankfully] comes up with a crash report. I've tried throwing my options.txt and .bin into the trash, and force updating in every possible way, (I even re-installed the client) yet it still crashes upon clicking on the options tab. And yes, my client was completely un-modded when this occurred. Regardless with it modded or not, it still crashes. I'm thinking this might be an issue with my computer system, but then again, I have no idea. As displayed below, my java version is updated to the highest possible on my computer (still valid with mc, as it's above java 5).
My complete crash report is viewable below and can be downloaded.
And yes, I have already submitted this issue to the "official bug reporting website" monitored by the devs. They said it was a duplicate of other problems, unfortunately linking me to other solutions that consisted of "just force update your client," which, as stated above, I have already done.
VVV Original crash report posted on the official mojang bug reporting forum, as stated above.
https://mojang.atlas...ql=project = MC
Crash Report:
https://mojang.atlas...5.58-client.txt
System Specifications:
-Year = Not sure what year this computer is from, as it's from a friend's computer lab, but it's definitely over 7 years old. (Just for clarification, this computer is definitely not too old to run minecraft, as it was running it just fine earlier this morning, and has been for as long as beta was introduced.
-Type = Mac Tower (Not sold anymore, but similar to that of a Mac pro). Basically a Monitor hooked up to a tower or computer unit.
-OSX Version = 10.6.8
-Java Version = 1.6.0 (aka. Java 6). Yes, I'm running Snow Lepoard, not Lion, as Java 7 doesn't support any operating system lower than Lion.
I can attempt to provide more information about my mac if needed, but I don't think my system is the issue, as once again this was perfectly fine this morning. I'm guessing it's a problem with my .minecraft folder. What seems interesting is the fact that force updating won't include all of the necessary files in a default un-modded client (just to name some, the sound files weren't all included. I had to install them manually) which is why i'm assuming the problem is not with my system.
Any and all help is appreciated. Thank you for your time.
-
View User Profile
-
View Posts
-
Send Message
Retired Staffhttp://assets.minecraft.net/1_5_2/minecraft.jar
Replace that with the one you have in your Minecraft directory. Does it still occur?
Analyzing the crash report, it seems that I am missing a class file, most likely indicating that my .jar is corrupt, so you're on the right track. The issue is probably along the lines of my .jar.
Like i said at the top, (even though that might work) it was still working perfectly fine this morning. Unless my computer "cracked," I don't see a reason why it wouldn't work now...
EDIT: Thinking back to what I was doing, since I was force-updating my jar dozens of times due to mods, something in my jar must have screwed up, meaning again, my .jar might be corrupt. Something in my computer might be blocking parts of the jar during the force update... I'll check on my firewall, etc.