GitLab very slow and unable to expand menus

[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)

[roru2k20]

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?

[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.

[roru2k20]

@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

[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.

[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.

[girish]

@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.