1
Solved

OutOfMemoryException when refreshing the dashboard

The tray icon does not update itself.

When I click on the refresh icon in the dashboard I get an OutOfMemory exception popup.

My machine has 64GB of memory and definitely did not run out of memory.
Looking at the logs there seems to be an issue with deserialization.

Attached is a screenshot of the issue and the logs.

Follow

6 replies

Votes Newest Oldest
AT

After I posted I realised that the GitLab settings appeared red with an OutOfMemoryException error.

I was using the default "https://gitlab.com" server address and that kind of worked and pulled some data, but only once.

When I put "https://gitlab.com/<my organization>" the error went away and refresh works.

Comment
1

Thanks for reporting this!

What is the memory usage of LocalWeb process when you see those memory limit errors? (this process is part of CatLight app)

The main reason why this can happen with GitLab connections is that we cache GitLab responses in memory to avoid DDOS-ing the service with frequent requests. If those responses are very large, the process can use a lot of memory and run out of it. We did some caching improvements for GitLab a few months ago, but apparently, the issue still happens.

One way to avoid it is to monitor fewer spaces in GitLab, but we'll look into better solutions.

Comment
AT

Here's a screenshot of the memory usage when the app gave me an OutOfMemoryException.

I've got 64GB of RAM and it was only at 70% load when the issue happened.

When the issue comes up the settings for the GitLab server connection are also marked as in error and the token is wiped out.
Could it be that the app doesn't store the path properly (as I set the root gitlab URL initially)?

I only monitor 4 projects. Is that too much?
They have associated CI pipelines so there are a lot of builds every day.Cheerimage-1718626736926.png

Comment

Please try 3.6.1+ , we made a couple of improvements in Gitlab response caching that might help - https://catlight.io/downloads 

CatLight currently runs as a 32-bit process, so it's max memory consumption is limited at around 1.2 GB at peak.

Comment

We found the root cause of the issue - there was a memory leak for GitLab connections that could result in high memory and CPU usage after about an hour of running.

It should be fixed in 3.7.2 https://catlight.io/downloads  

Comment
AT

Hey,

Just wanted to say "thank you".

I installed the update you mentioned above and haven't seen any issue since.

Cheers.

Comment
Reply