---- Minecraft Crash Report ---- // Hey, that tickles! Hehehe! Time: 8/9/14 9:19 AM Description: Exception in server tick loop java.lang.OutOfMemoryError: Java heap space at dq.<init>(SourceFile:8) at dy.a(SourceFile:75) at dh.a(SourceFile:326) at dh.a(SourceFile:41) at dq.a(SourceFile:37) at dh.a(SourceFile:329) at dh.a(SourceFile:41) at dh.a(SourceFile:329) at dh.a(SourceFile:41) at du.a(SourceFile:120) at du.a(SourceFile:89) at du.a(SourceFile:85) at aqk.a(SourceFile:60) at ms.f(SourceFile:125) at ms.c(SourceFile:78) at net.minecraft.server.MinecraftServer.g(SourceFile:250) at bsx.a(SourceFile:83) at bsx.e(SourceFile:99) at net.minecraft.server.MinecraftServer.run(SourceFile:339) at lj.run(SourceFile:628) A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- System Details -- Details: Minecraft Version: 1.7.10 Operating System: Windows 7 (x86) version 6.1 Java Version: 1.7.0_67, Oracle Corporation Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation Memory: 104253536 bytes (99 MB) / 523501568 bytes (499 MB) up to 523501568 bytes (499 MB) JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used IntCache: cache: 0, tcache: 0, allocated: 13, tallocated: 95 Profiler Position: N/A (disabled) Vec3 Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used Player Count: 0 / 8; [] Type: Integrated Server (map_client.txt) Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.