---- Minecraft Crash Report ---- // Daisy, daisy... Time: 1/15/14 10:28 PM Description: Exception in server tick loop java.lang.OutOfMemoryError: Java heap space at java.lang.String.concat(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at qr.e(SourceFile:1040) at qr.d(SourceFile:1010) at apb.a(SourceFile:209) at apb.a(SourceFile:96) at ml.b(SourceFile:146) at ml.a(SourceFile:175) at mm.a(SourceFile:604) at net.minecraft.server.MinecraftServer.a(SourceFile:276) at net.minecraft.server.MinecraftServer.t(SourceFile:458) at btk.t(SourceFile:117) at net.minecraft.server.MinecraftServer.run(SourceFile:357) at lb.run(SourceFile:616) A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- System Details -- Details: Minecraft Version: 1.7.4 Operating System: Windows 8 (x86) version 6.2 Java Version: 1.7.0_45, Oracle Corporation Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation Memory: 17776848 bytes (16 MB) / 518979584 bytes (494 MB) up to 518979584 bytes (494 MB) JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M AABB Pool Size: 770957 (43173592 bytes; 41 MB) allocated, 9849 (551544 bytes; 0 MB) used IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94 Profiler Position: N/A (disabled) Vec3 Pool Size: 1944 (108864 bytes; 0 MB) allocated, 1845 (103320 bytes; 0 MB) used Player Count: 1 / 8; [mp['robertbradley'/441, l='bunker', x=91.12, y=69.00, z=380.72]] Type: Integrated Server (map_client.txt) Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.