Awright, recently tried to get minecraft for self and friend to play - mostly 2 ppl on server, max 4. Tried to make a modpack for latest mc, failed at 1.7.10, so got 1.7.2 with all the latest possible mods etc, specced for 1.7.2 from their offsites. (will list em all in spoiler) Thing is that after running just like 1500 in any dir (without yet anything built - just exploring for a site) done by either me (host) or friend, the server first lags heavily on item pickup attempts, then goes boom with "Caused by: java.lang.OutOfMemoryError: Java heap space". Cannot point exactly which mods of my pack cause this, it seemed to work with just the industrial craft, might be railcraft (involved in terrain alterations). My own user research got 2 half-answers to the problem:
1) allocate more heap memory to server application (can't find how)
2) kill some of the installed mods cuz they are some otherwordly crap
Now as for (2) mods will be listed in spoilers and you can judge if anything is wrong, so I will only mention the memory thing separately. All applications related to minecraft are labeled jawaw in task manager and their properties get me to jawa SE launcher. First hint I got from one forum - through control panel adjust memory for all jawaw applets via -XINCGC -XMX(5000)M. Did that - my client stopped freezing and agonizing close to server fail BUT server fail still occurs as the server aplet seems to be nailed to 256 mb memory and never exceeding that in task list, despite the above mentioned change. So on other forums ppl advised to add
java -Xmx1024M -Xms1024M -jar minecraft_server.jar
to the server startup lines. Problem is that I can't find the server startup lines and where to put this change in.
Thanks in advance for answering and sorry if anything asked is completely trivial.
Crash log of the server:
List of programs and mods (all of them were freshly completely reinstalled today to check that bug persists despite that)
clients:
Server:
P.S. Once again noting that general java memory allocation command really impacted my client behavior and memory consumption in tasks window, but did not affect server memory usage - kept at 256mb. Thanks for reading.