Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    ProGet in docker/linux hanging after using all memory

    Scheduled Pinned Locked Moved Support
    6 Posts 2 Posters 23 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P Offline
      patchlings
      last edited by

      Hello.

      We run proget in a container on linux. We experience that the proget container consumes more and more memory (looking at the mono.exe process it runs) and then finally freezes once all memory on host machine is consumed. Only solution then is to restart the container (not the DB container, which is running fine). We have a 8GB host linux machine. Almost all of that memory is consumed by the proget container.
      It really does seem like a memory leak. We are currently, using crontab, restarting the container every day as a workaround.

      Do you have any idea what could be causing this and how we can proceed in troubleshooting it?

      1 Reply Last reply Reply Quote 0
      • atrippA Offline
        atripp inedo-engineer
        last edited by

        Hello; we haven't had any other users report this, so I'm afraid I don't have any idea how to help. It certainly sounds like a memory leak, and it'st most definitely a mono-specific bug; unfortunately these are extremely hard to track down, and sometimes are even platform specific (i.e. depending on host operating system).

        I would make sure to upgrade to latest version of container image.

        If you're not already using SQL Server for Linux (and you're using Postgres), then switch to SQL Server.

        I would simplify configuration; if you have a lot of connectors, etc.

        Try putting a ngix proxy infront of it.

        Once we have a clue about where the mono-bug is, we can at least consider ways to work-around it.

        P 1 Reply Last reply Reply Quote 0
        • P Offline
          patchlings @atripp
          last edited by patchlings

          Thanks for the answer!

          @atripp said in ProGet in docker/linux hanging after using all memory:

          Hello; we haven't had any other users report this, so I'm afraid I don't have any idea how to help. It certainly sounds like a memory leak, and it'st most definitely a mono-specific bug; unfortunately these are extremely hard to track down, and sometimes are even platform specific (i.e. depending on host operating system).

          I would make sure to upgrade to latest version of container image.

          If you're not already using SQL Server for Linux (and you're using Postgres), then switch to SQL Server.

          We use SQL Server.

          I would simplify configuration; if you have a lot of connectors, etc.

          We have 3 feeds and 2 connectors.

          Try putting a ngix proxy infront of it.

          We have that! =).

          Once we have a clue about where the mono-bug is, we can at least consider ways to work-around it.

          Yes. Maybe someone else have clues or have seen something similar. Most "linux container progets" run mono.exe right?

          BR

          atrippA 1 Reply Last reply Reply Quote 0
          • atrippA Offline
            atripp inedo-engineer @patchlings
            last edited by

            @patchlings said in ProGet in docker/linux hanging after using all memory:

            Most "linux container progets" run mono.exe right?

            Actually, all of them run mono.exe. We've had some people build a WINE-version of our products as a container, but I'm not sure if that's any better...

            1 Reply Last reply Reply Quote 0
            • P Offline
              patchlings
              last edited by

              Looking at the mono process it grows to more than 2 GB Resident memory on one day. Is there any number to compare this to?

              1 Reply Last reply Reply Quote 0
              • atrippA Offline
                atripp inedo-engineer
                last edited by

                Not in particular; .NET does garbage collection, in the background, as needed; so it's not uncommon to see processes "swell" to consume available memory and then "contract" overtime, as memory usage (percentage-wise) gets high.

                1 Reply Last reply Reply Quote 0

                Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                With your input, this post could be even better 💗

                Register Login
                • 1 / 1
                • First post
                  Last post
                Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation