I could be wrong - but did you notice the first line of the crash log
There is insufficient memory for the Java Runtime Environment to continue.
and further down it give some suggestions
Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
How much memory has your PC got free, how much have you assigned to Minecraft & how much is assigned to JAVA ?
As far as I can see you have 32Gb memory but with only 3Gb memory free (with a 62Gb Swap file with only 0.04 of it free).
Also I can't tell if you're using 64-bit JAVA or only 32-Bit Java (I'm not expert at reading crash logs btw)
so I have a 64 bit operating system and 3 gb of ram free and total of 4 gb of ram and I allocate 1 to Minecraft because whenever I allocate more than 1 for eg 2 it will just crash straight away
# Set larger code cache with -XX:ReservedCodeCacheSize=
Rollback Post to RevisionRollBack
Say something silly, Laugh 'til it hurts, Take a risk, Sing out loud, Rock the boat, Shake things up, Flirt with disaster, Buy something frivolous, Color outside the lines, Cause a scene, Order dessert, Make waves, Get carried away, Have a great day!
This looks a lot like a similar issue somebody else had recently; in both cases it appears that there wasn't enough swap space left (Java is very sensitive to this and known to fail if there isn't enough swap even if there is enough physical memory); the JVM tried to allocate 32 MB of memory when there was only 5 MB of swap remaining:
# Native memory allocation (mmap) failed to map 33554432 bytes for Failed to commit pages from 106496 of length 8192
You say that you have 3 GB free and have allocated 1 GB but this shows only 366 MB free, and only 5 MB of free swap; what else are you running? These numbers seem really high given that I've never had any issues like this on a computer with a 32 bit OS with 3.2 GB of usable memory, including much lower memory/swap usage (if your computer only has 4 GB installed it is really best to use a 32 bit OS since 64 bit programs need more memory; the system requirements for Windows 10 are 1 GB for 32 bit and 2 GB for 64 bit).
I've never had any issues like this on a computer with a 32 bit OS with 3.2 GB of usable memory, including much lower memory/swap usage (if your computer only has 4 GB installed it is really best to use a 32 bit OS since 64 bit programs need more memory; the system requirements for Windows 10 are 1 GB for 32 bit and 2 GB for 64 bit).
Why in the world would you be using a 32 bit OS in 2018?!?!?!?!?!
so should I download 32 bit java cause I understand what everyone is saying but I don't exactly know what to fix the crash
This will likely not fix the issue; as mentioned in the report, try allocating less memory; 512 MB should be enough given that the crash report showed that only 224 MB was actually being used. However, since the JVM was only using this much and not the maximum 1 GB available this may not actually change anything; as mentioned before, your computer seems to have a lot of things going on in the background since it is nearly out of memory, both physical and swap (only 5 MB free; this means that the system cannot allocate more memory, even virtual memory); for example, do you have a browser running?
For example, this is what my computer is currently using; the memory usage by Firefox is comparable to what Java uses when running 1.6.4 with 512 MB allocated (memory usage should not be higher with 1 GB or more unless the JVM actually allocates all of it; I see a peak allocation (in F3) of around 350 MB after several hours of playing. The JVM may still have to be able to reserve the maximum amount of heap memory, hence the "could not create the Java virtual machine" error when allocating more than 1.5 GB or so on a 32 bit system, and possibly 64 bit if there aren't enough resources):
here is the crash report
https://pastebin.com/jJuNkc9z
I could be wrong - but did you notice the first line of the crash log
and further down it give some suggestions
Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
How much memory has your PC got free, how much have you assigned to Minecraft & how much is assigned to JAVA ?
As far as I can see you have 32Gb memory but with only 3Gb memory free (with a 62Gb Swap file with only 0.04 of it free).
Also I can't tell if you're using 64-bit JAVA or only 32-Bit Java (I'm not expert at reading crash logs btw)
so I have a 64 bit operating system and 3 gb of ram free and total of 4 gb of ram and I allocate 1 to Minecraft because whenever I allocate more than 1 for eg 2 it will just crash straight away
Yun run out of free RAM.
See this again:
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
This looks a lot like a similar issue somebody else had recently; in both cases it appears that there wasn't enough swap space left (Java is very sensitive to this and known to fail if there isn't enough swap even if there is enough physical memory); the JVM tried to allocate 32 MB of memory when there was only 5 MB of swap remaining:
You say that you have 3 GB free and have allocated 1 GB but this shows only 366 MB free, and only 5 MB of free swap; what else are you running? These numbers seem really high given that I've never had any issues like this on a computer with a 32 bit OS with 3.2 GB of usable memory, including much lower memory/swap usage (if your computer only has 4 GB installed it is really best to use a 32 bit OS since 64 bit programs need more memory; the system requirements for Windows 10 are 1 GB for 32 bit and 2 GB for 64 bit).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
so what should I do exatcly
Why in the world would you be using a 32 bit OS in 2018?!?!?!?!?!
I cannot use this account anymore
so should I download 32 bit java cause I understand what everyone is saying but I don't exactly know what to fix the crash
This will likely not fix the issue; as mentioned in the report, try allocating less memory; 512 MB should be enough given that the crash report showed that only 224 MB was actually being used. However, since the JVM was only using this much and not the maximum 1 GB available this may not actually change anything; as mentioned before, your computer seems to have a lot of things going on in the background since it is nearly out of memory, both physical and swap (only 5 MB free; this means that the system cannot allocate more memory, even virtual memory); for example, do you have a browser running?
For example, this is what my computer is currently using; the memory usage by Firefox is comparable to what Java uses when running 1.6.4 with 512 MB allocated (memory usage should not be higher with 1 GB or more unless the JVM actually allocates all of it; I see a peak allocation (in F3) of around 350 MB after several hours of playing. The JVM may still have to be able to reserve the maximum amount of heap memory, hence the "could not create the Java virtual machine" error when allocating more than 1.5 GB or so on a 32 bit system, and possibly 64 bit if there aren't enough resources):
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
omg thx so much dude I just cleard some stuff of my desktop and I went from having 600 mb free to 1.6 gb free thanks so much
the crash has come back I don't know whats wrong but I have 1.6 GB available and only 1 gb allocated
Post a dxdiag log http://hopper.minecraft.net/help/pixel-format-not-accelerated/support/
here is the dxdiag log https://pastebin.com/1VMTW3Uu