[Dario Lombardo <lomato@xxxxxxxxx>]

Gitlab runs a background _javascript_ jobs that pulls the server for new comments on a issue. This way they appear to your window as soon as they have been created by a concurrent user. This gives a good user experience and is easily seen in the browser debugger/network window. This could be the reason why it eats up some memory/CPU, despite from your description it seems too much.

On Wed, Aug 26, 2020, 08:43 Guy Harris <gharris@xxxxxxxxx> wrote:

I have *NO* idea what the hell GitLab is doing, but, in Safari, if I have a GitLab window open and not minimized to the Dock, the Safari Networking process chews up about 1/3 of a core (~33% CPU) doing a ton of crap with cookies).  Minimizing the window to the Dock reduces the Safari Networking CPU usage to a low level, as does closing the window; de-minimizing the window causes it to fire up again.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe