Out of memory on 1.6.4

Discussion in 'Bukkit Help' started by gorzek, Nov 20, 2013.

Thread Status:
Not open for further replies.
  1. Offline

    gorzek

    I've seen indications in a few places that the map format was changed as of 1.6.4, which means pre-1.6.4 maps are handled differently. However, I wanted to get a clear answer.

    I can run 1.6.2 without issues on my server. When I run 1.6.4, I run out of RAM while spawn areas are being prepared for each world, and it crashes the application. The preparation process also takes much longer in 1.6.4 than it does in 1.6.2. I have several worlds, all of which are pre-1.6.4.

    Throwing more memory at it is not an ideal solution for me, due to cost. I'd also rather not wipe out my maps if I can avoid it. Is there some other solution? I already tried disabling all plugins--it doesn't really help. It's the initial startup where spawn areas are prepared that's sucking up all the RAM, so it doesn't even get around to plugins.

    My apologies if there is already a thread/solution about this. Thanks for any help you can provide.
     
  2. Offline

    Mr_gav

    How much ram do you have?
     
  3. Offline

    gorzek

    I have a gigabyte of physical RAM and then 2GB of swap. 1.6.2 usually tops out at around 800MB total usage, with all my typical plugins. How far beyond that 1.6.4 would go, I don't know, but clearly it's above 1GB.
     
  4. Offline

    Mr_gav

    If you are on a VPS the OS will take some ram up as well (windows will take like 200mb to 500mb) on a shared host that isn't a issue however the world size in it's self can affect this too.

    I have a 300GB world and it takes 20GB of ram just to start. It is very possible that it isn't the update and that it is world size. Or a mass amount of entities as well, with worldguard you can use /stoplag to clear entites. Let me know how that goes.

    Also bukkit itself uses more ram, try removing bukkit and starting and see if that works.
     
  5. Offline

    gorzek

    Right, the 800MB was total with OS and everything (it's a VPS.) My worlds are pretty big, but as I said, 1.6.2 works perfectly fine. It's going to 1.6.4 that makes it run out of RAM on startup. If I roll back to 1.6.2, it's still fine.

    My largest world is 1.4GB, so it's not enormous.
     
  6. Offline

    Mr_gav

    Have you tried removing bukkit and starting 1.6.4? That takes up ram as well.
     
  7. Offline

    gorzek

    No, I haven't tried vanilla yet. Good idea. I'll let you know the results.
     
  8. Offline

    gorzek

    OK, I tried vanilla 1.6.4. It worked, but I noticed two things:

    • Memory usage was definitely much higher than in the past.
    • CPU usage was very, very high, the server often pegged at 100% with no users on.
    Is this normal? Should I just chalk it up as a 1.6.4 bug in Minecraft itself, unrelated to CB?
     
  9. Offline

    jeffro1001

    what 1.6.4 build number are you using?

    try using build #2919 and see how it does.
     
  10. Offline

    gorzek

    I'm running #2918. #2919 has only a tag change, no code changes. It wouldn't be any different in terms of performance.
     
Thread Status:
Not open for further replies.

Share This Page