Minecraft has crashed!
----------------------
Minecraft has stopped running because it encountered a problem; Failed to start game
A full error report has been saved to /Users/andyrudd/Library/Application Support/minecraft/crash-reports/crash-2013-04-07_15.05.35-client.txt - Please include a copy of that file (Not this screen!) if you report this crash to anyone; without it, they will not be able to help fix the crash :(
--- BEGIN ERROR REPORT dc447bc7 --------
Full report at:
/Users/andyrudd/Library/Application Support/minecraft/crash-reports/crash-2013-04-07_15.05.35-client.txt
Please show that file to Mojang, NOT just this screen!
Generated 4/7/13 3:05 PM
-- System Details --
Details:
Minecraft Version: 1.5.1
Operating System: Mac OS X (x86_64) version 10.7.5
Java Version: 1.6.0_43, Apple Inc.
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Apple Inc.
Memory: 386957752 bytes (369 MB) / 534708224 bytes (509 MB) up to 1065025536 bytes (1015 MB)
JVM Flags: 3 total; -Xbootclasspath/a:/System/Library/PrivateFrameworks/JavaApplicationLauncher.framework/Resources/LauncherSupport.jar -Xms512M -Xmx1024M
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Suspicious classes: No suspicious classes found.
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
LWJGL: 2.4.2
OpenGL: ATI Radeon HD 6770M OpenGL Engine GL version 2.1 ATI-7.32.12, ATI Technologies Inc.
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Texture Pack: Inter Realistic Texture Pack 512
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
bio
at bin.d(SourceFile:84)
at bis.b(SourceFile:95)
at bgf.d(SourceFile:350)
at net.minecraft.client.Minecraft.a(SourceFile:298)
at avv.a(SourceFile:56)
at net.minecraft.client.Minecraft.run(SourceFile:507)
at java.lang.Thread.run(Thread.java:680)
--- END ERROR REPORT 4b0d7407 ----------Linked issues
is duplicated by 18
Attachments
Comments 10
Understood, but that path is not set up on my Mac, so I am unable to locate where the error report was saved.
Sorry if this didn't help, i don't have a Mac, never used it for anything, but this might help a bit:
/minecraft/crash-reports/crash-2013-04-07_15.05.35-client.txt
1. Lets start with the first: /minecraft/. I think you know where it's located at?
2. /crash-reports/. In /minecraft/, look for "Crash Reports" or "crash_reports", or something like this.
3. look at the name, try to recognize it and find it.
4. Post it here.
No path needs to be set up. Just go to your user folder (andyrudd) then to the folder called Library, then Application Support, then minecraft, then crash-reports.
Although it is hidden, OS X allows you to access it if you know the path. In this case, open Finder, click Go > Go to Folder..., type ~/Library/Application Support/minecraft/crash-reports/ and click Go. Attach the crash-2013-04-07_15.05.35-client.txt file here (or whichever file the crashlog pointed to).
The issue seemed to be fixed by removing all of the texturepacks from the Library Application Support files and deleting old Minecraft. I reloaded and it worked. My son then downloaded Realistic Texturepack and it crashed again. After discarding the Realistic folder from the Library/application support/minecraft/texturepack folder, it worked again. No more Realistic for us. For Mac users that are unfamiliar with Library, open Folder then hold down the option key while clicking Go then Library in the top dropdown.
I was directed here by a comment that said my question was a duplicate to this one.
I have found and erased a "texturepack" file that you mention here, and it seems to be the cure. Thank you. We will try to avoid such additions since they seem to destroy Minecraft.
I wonder why Minecraft says it is version 1.0.0 in the "About" window at the beginning, yet after opening it calls itself 1.5.2 in the lower left corner, which is confusing and at first prevented me form even posting a question since I listed 1.0.0 as the version and that was refused by this questionnaire page.
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
A full error report has been saved to /Users/andyrudd/Library/Application Support/minecraft/crash-reports/crash-2013-04-07_15.05.35-client.txt - Please include a copy of that file (Not this screen!) if you report this crash to anyone; without it, they will not be able to help fix the crash