I'm sure this has been covered before, but after three days of digging here and in other forums I can't seem to find a definitive answer. I play MC mostly on my old laptop: Windows Vista 32-bit, 4GB RAM (1GB set aside for Radeon HD2600)... if we need complete system specs let me know. Anyway, I've played most of the main Technic mod packs without any issues, and several of the mod packs in Feed The Beast. We've been running a small server for 3 or 4 players, and we ran Hexxit for a while, and even added some mods to our Hexxit server and clients. Still, no issues. After that, we were running FTB Horizons for about a month and still no issues on my laptop (Not serving on the laptop, just the client side).
Everybody in our little group has started finding their favorite mods, and of course we're all finding mods we agree we don't want, so I started putting together a sort of custom mod pack on a fresh install of MC and using 1.6.4. My problem comes in when I get between 80 and 85 mods. I run the client, start a new world (so new mods can generate in the world for testing), and when the console is done preparing the spawn area, the MC window goes to the dirt background andshuts down the internal server. Then, of course, the 'Java has run out of memory' screen pops up. I would think it's just because I'm using too many mods, but Hexxit and most of the FTB modpacks have more. FTB Horizons has 109 mods and I run it with no major problems!
So, that said... am I actually running out of memory? Task Manager resource monitor tells me I'm using about 73% of available RAM. Does this have to do with the mods I'm selecting? Could incompatible mods cause a memory issue? If I list the mods I would like to use, would someone be able to point at the list and say "those two mods don't work together!" ?? Any ideas? Thanks in advance!
Thanks for the response! Unfortunately, in the time since I posted, I got a new laptop. Issue solved! Is there some way I can edit or remove the first post to show people that there won't be much enlightenment in this thread?
I will say thought, I think it was just the amount of mods in a 1.6.4 pack, on a 32-bit system. I played Hexxit with no major problems, and that's a 1.5.2 with a lot of mods, and at one point we had added some, bringing it up around 140 mods. It was after I posted here that I really started paying attention to 1.6.4 modpack notes that were stating things like 'the amount of mods in this pack need at least 2 gigs of ram or it will crash'. 4 gigs of RAM on a 32-bit system... that was NOT going to happen.
You can press the report button at the bottom of each post and then tell the moderator whatever you want them to do such as delete posts or the whole topic in general.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Everybody in our little group has started finding their favorite mods, and of course we're all finding mods we agree we don't want, so I started putting together a sort of custom mod pack on a fresh install of MC and using 1.6.4. My problem comes in when I get between 80 and 85 mods. I run the client, start a new world (so new mods can generate in the world for testing), and when the console is done preparing the spawn area, the MC window goes to the dirt background andshuts down the internal server. Then, of course, the 'Java has run out of memory' screen pops up. I would think it's just because I'm using too many mods, but Hexxit and most of the FTB modpacks have more. FTB Horizons has 109 mods and I run it with no major problems!
So, that said... am I actually running out of memory? Task Manager resource monitor tells me I'm using about 73% of available RAM. Does this have to do with the mods I'm selecting? Could incompatible mods cause a memory issue? If I list the mods I would like to use, would someone be able to point at the list and say "those two mods don't work together!" ?? Any ideas? Thanks in advance!
I will say thought, I think it was just the amount of mods in a 1.6.4 pack, on a 32-bit system. I played Hexxit with no major problems, and that's a 1.5.2 with a lot of mods, and at one point we had added some, bringing it up around 140 mods. It was after I posted here that I really started paying attention to 1.6.4 modpack notes that were stating things like 'the amount of mods in this pack need at least 2 gigs of ram or it will crash'. 4 gigs of RAM on a 32-bit system... that was NOT going to happen.
Thanks again!