long time minecraft player(3rd account lost the first 2), modded and unmodded. I haven't had an issue like this before. I'm not sure if its a memory leak to be completely honest but I don't really have another explanation as to why it's doing what its doing
here's what its doing once I launch and load up minecraft, upon looking into task manager this pops up
it's using almost 10gigs of memory which is quite tragic, albeit I can still play minecraft with no issues it limits me wanting to do other things
next issue, when I close minecraft in general(not ending process) I'm left with a ghost javaw.exe using about 6gigs of memory
this made zero sense to me, and it stays open indefinitely until I end the process via task manager. I haven't figured out how to open the process, it doesn't show up in applications so I can't just close and play on the ghost version, so I have no idea where its sitting at on my computer, its just there.
upon closing this ghost minecraft via end process this pops up from my launcher
it says my game crashed, which is a lie since there was no game to crash in the first place. I have no crash logs on this so I can't give them for you to figure out
I'm currently running 170mods, and normally I use about 5-6gigs max through cmd. Inside of minecraft actually playing it's only using about 3gig.
This is an extreme example of what I was just explaining, and it made no sense to me, and it's also when I noticed the issue in cmd when I closed minecraft and found the ghost application just running
so if anyone has any solutions or can help me figure this out, that'd be pretty stellar. The issue came from when I went from running the mods via curse or other launchers like technic, to running installing the mods and using them myself
some more information I can provide, while watching minecraft load up and watching the memory, it goes up and down between 1gig and 3gigs until it loads up Minecraft ChromiumEF than it shoots up to 9-10gigs
The Meaning of Life, the Universe, and Everything.
Location:
Somewhere
Join Date:
12/30/2013
Posts:
114
Location:
United States
Minecraft:
sam_86314
Xbox:
nope
PSN:
nope
Member Details
Allocate less memory to the game. Minecraft can't really seem to handle having more than 4GB allocated.
I noticed that the allocated memory in the F3 menu and the memory usage in the task manager were similar. I suspect that the allocated memory line means that the game is reserving that amount of RAM for when it needs it. That would mean nothing else could use it, and it would show that Minecraft would be using all that memory in task manager.
some more information I can provide, while watching minecraft load up and watching the memory, it goes up and down between 1gig and 3gigs until it loads up Minecraft ChromiumEF than it shoots up to 9-10gigs
This is most likely an issue with ChromiumEF then; both the memory usage as well as not closing properly. Also, as mentioned by others, you should allocate less memory as allocating far more than the game actually needs is both wasteful (nothing else can use it, even if the game is only using a fraction of it) and slows down the game (even going from just 512 MB to 1 GB can make a difference. Well-coded mods should not need more than this; of course, that is rarely the case).
This is most likely an issue with ChromiumEF then; both the memory usage as well as not closing properly. Also, as mentioned by others, you should allocate less memory as allocating far more than the game actually needs is both wasteful (nothing else can use it, even if the game is only using a fraction of it) and slows down the game (even going from just 512 MB to 1 GB can make a difference. Well-coded mods should not need more than this; of course, that is rarely the case).
Agreed, he should report this as a bug on the MCEF topic: Here
Rollback Post to RevisionRollBack
I just took the Minecraft Noob test! Check out what I scored. Think you can beat me?!
To take the test, check out https://minecraftnoobtest.com/test.php
I made a post last year when I started running into issues pertaining to high memory use, and I will link to it in case it provides any helpful insight.
In short, once you start using dozens upon dozens of mods, long render distances, and/or especially allocating a lot of RAM to Java, your PCs RAM use can go way up when using Minecraft. It will allocate at least as much, often more, RAM from your PC that you allocate to Java (irregardless of what Minecraft in-game says it is using), and at least from what I was guessing in my own post there, maybe video card VRAM (like on ones with a lot of VRAM) may come into play? At least, I was "running out" of RAM at 10 GB on a 16 GB PC with a 6 GB VRAM video card, which seemed a bit coincidental to me... but I don't know what was really happening.
For what it's worth, my RAM use seems a bit lower now even though I still allocate 4 GB (I need to), although raising my virtual memory a bit stopped those warnings from showing.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
long time minecraft player(3rd account lost the first 2), modded and unmodded. I haven't had an issue like this before. I'm not sure if its a memory leak to be completely honest but I don't really have another explanation as to why it's doing what its doing
here's what its doing once I launch and load up minecraft, upon looking into task manager this pops up
it's using almost 10gigs of memory which is quite tragic, albeit I can still play minecraft with no issues it limits me wanting to do other things
next issue, when I close minecraft in general(not ending process) I'm left with a ghost javaw.exe using about 6gigs of memory
this made zero sense to me, and it stays open indefinitely until I end the process via task manager. I haven't figured out how to open the process, it doesn't show up in applications so I can't just close and play on the ghost version, so I have no idea where its sitting at on my computer, its just there.
upon closing this ghost minecraft via end process this pops up from my launcher
it says my game crashed, which is a lie since there was no game to crash in the first place. I have no crash logs on this so I can't give them for you to figure out
I'm currently running 170mods, and normally I use about 5-6gigs max through cmd. Inside of minecraft actually playing it's only using about 3gig.
This is an extreme example of what I was just explaining, and it made no sense to me, and it's also when I noticed the issue in cmd when I closed minecraft and found the ghost application just running
so if anyone has any solutions or can help me figure this out, that'd be pretty stellar. The issue came from when I went from running the mods via curse or other launchers like technic, to running installing the mods and using them myself
What version of java are you using? And what are your java arguments?
Cast aside your festive doylaks: dragon stuff is about to happen.
Multiplayer is lonely once you understand how it actually works.
Alpha 1.0.4
I just completely deleted and reinstalled java, so whatever the newest version is that's what I'm using
and these are my java arguments
full line here:
-Xmx12G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M
some more information I can provide, while watching minecraft load up and watching the memory, it goes up and down between 1gig and 3gigs until it loads up Minecraft ChromiumEF than it shoots up to 9-10gigs
Allocate less memory to the game. Minecraft can't really seem to handle having more than 4GB allocated.
I noticed that the allocated memory in the F3 menu and the memory usage in the task manager were similar. I suspect that the allocated memory line means that the game is reserving that amount of RAM for when it needs it. That would mean nothing else could use it, and it would show that Minecraft would be using all that memory in task manager.
CPU: Intel Core i7-2600K
GPU: Gigabyte GeForce GTX 1070 G1 Gaming
RAM: 16GB DDR3
HDD: 525GB SSD, 2TB and 4TB HDD
OS: Windows 10 Pro and Ubuntu 18.04.1 LTS
This is most likely an issue with ChromiumEF then; both the memory usage as well as not closing properly. Also, as mentioned by others, you should allocate less memory as allocating far more than the game actually needs is both wasteful (nothing else can use it, even if the game is only using a fraction of it) and slows down the game (even going from just 512 MB to 1 GB can make a difference. Well-coded mods should not need more than this; of course, that is rarely the case).
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?
Agreed, he should report this as a bug on the MCEF topic: Here
I just took the Minecraft Noob test! Check out what I scored. Think you can beat me?!
To take the test, check out
https://minecraftnoobtest.com/test.php
Don't click this link, HE is haunting it...
I made a post last year when I started running into issues pertaining to high memory use, and I will link to it in case it provides any helpful insight.
https://www.minecraftforum.net/forums/support/java-edition-support/2794819-minecraft-is-apparently-using-a-lot-of-memory-i
In short, once you start using dozens upon dozens of mods, long render distances, and/or especially allocating a lot of RAM to Java, your PCs RAM use can go way up when using Minecraft. It will allocate at least as much, often more, RAM from your PC that you allocate to Java (irregardless of what Minecraft in-game says it is using), and at least from what I was guessing in my own post there, maybe video card VRAM (like on ones with a lot of VRAM) may come into play? At least, I was "running out" of RAM at 10 GB on a 16 GB PC with a 6 GB VRAM video card, which seemed a bit coincidental to me... but I don't know what was really happening.
For what it's worth, my RAM use seems a bit lower now even though I still allocate 4 GB (I need to), although raising my virtual memory a bit stopped those warnings from showing.