Put the summary of the bug you're having here
---- Minecraft Crash Report ----
// I just don't know what went wrong

Time: 12/4/16 9:30 AM
Description: Initializing game

java.lang.OutOfMemoryError: Java heap space
at java.awt.image.DataBufferByte.<init>(DataBufferByte.java:92)
at java.awt.image.ComponentSampleModel.createDataBuffer(ComponentSampleModel.java:445)
at java.awt.image.Raster.createWritableRaster(Raster.java:941)
at javax.imageio.ImageTypeSpecifier.createBufferedImage(ImageTypeSpecifier.java:1074)
at javax.imageio.ImageReader.getDestination(ImageReader.java:2892)
at com.sun.imageio.plugins.png.PNGImageReader.readImage(PNGImageReader.java:1309)
at com.sun.imageio.plugins.png.PNGImageReader.read(PNGImageReader.java:1606)
at javax.imageio.ImageIO.read(ImageIO.java:1448)
at javax.imageio.ImageIO.read(ImageIO.java:1352)
at bvh.a(SourceFile:377)
at bve.a(SourceFile:219)
at bvd.a(SourceFile:190)
at bvd.b(SourceFile:149)
at bvd.a(SourceFile:76)
at bxo.m(SourceFile:727)
at bxo.a(SourceFile:172)
at bxp.a(SourceFile:23)
at bwi.a(SourceFile:100)
at bcc.an(SourceFile:513)
at bcc.a(SourceFile:377)
at net.minecraft.client.main.Main.main(SourceFile:124)

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

– Head –
Stacktrace:
at java.awt.image.DataBufferByte.<init>(DataBufferByte.java:92)
at java.awt.image.ComponentSampleModel.createDataBuffer(ComponentSampleModel.java:445)
at java.awt.image.Raster.createWritableRaster(Raster.java:941)
at javax.imageio.ImageTypeSpecifier.createBufferedImage(ImageTypeSpecifier.java:1074)
at javax.imageio.ImageReader.getDestination(ImageReader.java:2892)
at com.sun.imageio.plugins.png.PNGImageReader.readImage(PNGImageReader.java:1309)
at com.sun.imageio.plugins.png.PNGImageReader.read(PNGImageReader.java:1606)
at javax.imageio.ImageIO.read(ImageIO.java:1448)
at javax.imageio.ImageIO.read(ImageIO.java:1352)
at bvh.a(SourceFile:377)
at bve.a(SourceFile:219)
at bvd.a(SourceFile:190)
at bvd.b(SourceFile:149)
at bvd.a(SourceFile:76)
at bxo.m(SourceFile:727)
at bxo.a(SourceFile:172)
at bxp.a(SourceFile:23)
at bwi.a(SourceFile:100)
at bcc.an(SourceFile:513)

– Initialization –
Details:
Stacktrace:
at bcc.a(SourceFile:377)
at net.minecraft.client.main.Main.main(SourceFile:124)

– System Details –
Details:
Minecraft Version: 1.9.2
Operating System: Mac OS X (x86_64) version 10.10.5
Java Version: 1.8.0_74, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 19681296 bytes (18 MB) / 1060372480 bytes (1011 MB) up to 1060372480 bytes (1011 MB)
JVM Flags: 5 total; -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.9.2
LWJGL: 2.9.2
OpenGL: Intel HD Graphics 5000 OpenGL Engine GL version 2.1 INTEL-10.6.33, Intel Inc.
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because ARB_framebuffer_object is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.

Using VBOs: No
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: PureBDcraft 512x MC19
Current Language: English (US)
Profiler Position: N/A (disabled)
CPU: 4x Intel(R) Core(TM) i5-4260U CPU @ 1.40GHz
What I expected to happen was...:
Describe what you thought should happen here
I thought that Minecraft would open up and start just like usual.
What actually happened was...:
Describe what happened here
The MOJANG screen showed up for about one to two minuets and then showed the crash report.
Steps to Reproduce:
1. Put a step by step guide on how to trigger the bug here
2. ... Open Minecraft
3. ... Click the button that says Play
4. ... MOJANG screen shows up then crahes