Hopper: java.lang.OutOfMemoryError: GC overhead limit exceeded

This is an automatically generated report based from the following crash: http://hopper.minecraft.net/crashes/minecraft/MCX-465544/

Crash:

java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded

The following is the first clean report made public about this crash:

---- Minecraft Crash Report ----
// Everything's going to plan. No, really, that was supposed to happen.

Time: 10/25/13 9:45 AM
Description: Exception in server tick loop

java.lang.OutOfMemoryError: GC overhead limit exceeded
	at java.text.Format.format(Unknown Source)
	at org.apache.logging.log4j.core.pattern.DatePatternConverter.format(DatePatternConverter.java:166)
	at org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:36)
	at org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:167)
	at org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:52)
	at com.mojang.util.QueueLogAppender.append(QueueLogAppender.java:39)
	at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:99)
	at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:425)
	at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:406)
	at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:367)
	at org.apache.logging.log4j.core.Logger.log(Logger.java:110)
	at org.apache.logging.log4j.spi.AbstractLogger.error(AbstractLogger.java:581)
	at aoj.a(SourceFile:571)
	at aow.a(SourceFile:292)
	at aow.a(SourceFile:78)
	at aow.a(SourceFile:66)
	at mi.f(SourceFile:119)
	at mi.c(SourceFile:72)
	at mh.<init>(SourceFile:31)
	at mg.a(SourceFile:212)
	at mg.a(SourceFile:249)
	at ld.a(SourceFile:155)
	at ld.c(SourceFile:206)
	at ld.a(SourceFile:100)
	at nd.c(SourceFile:87)
	at nd.a(SourceFile:52)
	at ef.a(SourceFile:166)
	at ms.c(SourceFile:134)
	at net.minecraft.server.MinecraftServer.u(SourceFile:529)
	at net.minecraft.server.MinecraftServer.t(SourceFile:441)
	at bsk.t(SourceFile:117)
	at net.minecraft.server.MinecraftServer.run(SourceFile:358)


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- System Details --
Details:
	Minecraft Version: 1.7.2
	Operating System: Windows 7 (amd64) version 6.1
	Java Version: 1.7.0_45, Oracle Corporation
	Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
	Memory: 632949728 bytes (603 MB) / 776470528 bytes (740 MB) up to 954728448 bytes (910 MB)
	JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G
	AABB Pool Size: 1581 (88536 bytes; 0 MB) allocated, 1581 (88536 bytes; 0 MB) used
	IntCache: cache: 0, tcache: 0, allocated: 13, tallocated: 95
	Profiler Position: N/A (disabled)
	Vec3 Pool Size: 215 (12040 bytes; 0 MB) allocated, 215 (12040 bytes; 0 MB) used
	Player Count: 1 / 8; [mm['AtlasFallen'/522, l='Zone', x=-77.19, y=32.00, z=541.81]]
	Type: Integrated Server (map_client.txt)
	Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.

You can see this full report at http://hopper.minecraft.net/crashes/minecraft/MCX-465544/21349133/