Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. GitLab
  3. GitLab very slow and unable to expand menus

GitLab very slow and unable to expand menus

Scheduled Pinned Locked Moved GitLab
7 Posts 3 Posters 1.5k Views 2 Watching
  • 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.
  • R Offline
    R Offline
    roru2k20
    wrote on last edited by
    #1

    Hello,

    after the last update GitLab is very slow and unusable. I am using com.gitlab.cloudronapp@1.60.0

    I call the start page of a project and I get several minutes of progress circle.....
    And when I want to delete a project, I cannot expand a section. Other menus have the same behavior.

    My GitLab is running at home on an Intel(R) Pentium(R) CPU G4400T @ 2.90GHz with 16GB RAM and I have 6GB RAM allocated just for GitLab.

    I have restarted the application so many times, including the server itself.

    Does anyone have the same problem?

    Best wishes,
    Axel

    Translated with www.DeepL.com/Translator (free version)

    timconsidineT girishG 2 Replies Last reply
    1
    • R Offline
      R Offline
      roru2k20
      wrote on last edited by
      #2

      I thought I can restore the last version 1.59.2 but I have same issues.
      I can not expand any section on any menu point.

      May be my system is not good enough for GitLab?

      1 Reply Last reply
      0
      • R roru2k20

        Hello,

        after the last update GitLab is very slow and unusable. I am using com.gitlab.cloudronapp@1.60.0

        I call the start page of a project and I get several minutes of progress circle.....
        And when I want to delete a project, I cannot expand a section. Other menus have the same behavior.

        My GitLab is running at home on an Intel(R) Pentium(R) CPU G4400T @ 2.90GHz with 16GB RAM and I have 6GB RAM allocated just for GitLab.

        I have restarted the application so many times, including the server itself.

        Does anyone have the same problem?

        Best wishes,
        Axel

        Translated with www.DeepL.com/Translator (free version)

        timconsidineT Online
        timconsidineT Online
        timconsidine
        App Dev
        wrote on last edited by
        #3

        @roru2k20 I was having similar problems on cloudron's own gitlab (git.cloudron.io) for some time. So i don't think it is your own instance / machine specs. Seems to be performing better now.

        R 1 Reply Last reply
        2
        • timconsidineT timconsidine

          @roru2k20 I was having similar problems on cloudron's own gitlab (git.cloudron.io) for some time. So i don't think it is your own instance / machine specs. Seems to be performing better now.

          R Offline
          R Offline
          roru2k20
          wrote on last edited by
          #4

          @timconsidine thanks for reply.

          I read the problems at git.cloudron.io. With Microsoft Edge instead of my Chrome GitLab works fine.

          I observe it

          1 Reply Last reply
          0
          • R roru2k20

            Hello,

            after the last update GitLab is very slow and unusable. I am using com.gitlab.cloudronapp@1.60.0

            I call the start page of a project and I get several minutes of progress circle.....
            And when I want to delete a project, I cannot expand a section. Other menus have the same behavior.

            My GitLab is running at home on an Intel(R) Pentium(R) CPU G4400T @ 2.90GHz with 16GB RAM and I have 6GB RAM allocated just for GitLab.

            I have restarted the application so many times, including the server itself.

            Does anyone have the same problem?

            Best wishes,
            Axel

            Translated with www.DeepL.com/Translator (free version)

            girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by girish
            #5

            @roru2k20 I have noticed this as well. This appears to be some browser caching issue between GitLab updates. This is what I see:

            • I click on menu, it's not really opening.
            • I opened the firefox browser console, it has some error like this:
            Uncaught (in promise) TypeError: modules[moduleId] is undefined
                __webpack_require__ https://git.cloudron.io/assets/webpack/runtime.bundle.js:85
            
            • I load the page again
            • Menu opens instantly

            Can confirm that clearing browser cache fixes things ? Opening console/devtools clears the cache internally iirc.

            R 1 Reply Last reply
            3
            • girishG girish

              @roru2k20 I have noticed this as well. This appears to be some browser caching issue between GitLab updates. This is what I see:

              • I click on menu, it's not really opening.
              • I opened the firefox browser console, it has some error like this:
              Uncaught (in promise) TypeError: modules[moduleId] is undefined
                  __webpack_require__ https://git.cloudron.io/assets/webpack/runtime.bundle.js:85
              
              • I load the page again
              • Menu opens instantly

              Can confirm that clearing browser cache fixes things ? Opening console/devtools clears the cache internally iirc.

              R Offline
              R Offline
              roru2k20
              wrote on last edited by
              #6

              @girish it is very curious. At the moment it works well with this speed I think it is normal.

              And I clear my cache, cookies and more every quit of any browser.

              girishG 1 Reply Last reply
              1
              • R roru2k20

                @girish it is very curious. At the moment it works well with this speed I think it is normal.

                And I clear my cache, cookies and more every quit of any browser.

                girishG Offline
                girishG Offline
                girish
                Staff
                wrote on last edited by
                #7

                @roru2k20 I think there is a bug, either in packaging side or GitLab side that the web assets are not cleared on the browser side after an update. This happens on git.cloudron.io as well, so I am keep an eye out.

                1 Reply Last reply
                3
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Bookmarks
                • Search