XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Invalid
    • None
    • 1.18.1
    • Unconfirmed
    • (Unassigned)

      Hello there,

      I reported this problem to the general minecraft support page, but was sent here instead, this is my first time around this part of the community, so please ask clarifing questions if anything is not explained properly. I'll allow myself to copy the original issue ticket contents here.

      _Hello there,

      First of all, I cannot locate my trans. ID, the account has been purchased (if I'm not mistaken) around 2011. I'd have been 9 by then so the memories are kind of blured, but to the main topic;

      I've been running a server from around 1.8 to 1.16, I had to quit it for a while between 1.16 and 1.18 due to me moving to another city for uni. The server used to run pretty much 24/7 thanks to a UPS and DDNS just fime.

      The memory usage while idling was kind of perplexing to me, but it worked without any major hitches, so I didn't think much of it; a quick paint sketch of how the usage looked like: https://ibb.co/Jx0MkQ0

      But post update to minecraft 1.18 and Java 17 there appears to be a memory leak. The server runs fine for the first day or so, but after leaving it running for extented periods of time the 'java' process appears to be using more than the allocated amount of memory, and even after closing the server the RAM usage is enormous, even though no processes are running. Video showing the 'post close' state of RAM: https://youtu.be/8vvoPNbA5Q4

      Only restaring the entire machine helps to clear to ram. Could you please explain to me maybe what I'm doing wrong, or what changed were made in the versions I've been apsent (1.17/1.18) that could cause that? Also if possible instruct me what can be done to avoid that? Maybe I've been doing something wrong from the getgo and it only manifested now?

      Best regards, Julian_

            Unassigned Unassigned
            juleklO Julian
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: