Re: [Wireshark-dev] Pro tip, at least for Safari users - do not keep GitLab windows open and un-minimized any longer than necessary
On Aug 25, 2020, at 11:54 PM, Dario Lombardo wrote: > Gitlab runs a background javascript jobs that pulls the server for new > comments on a issue. That's not it. Having a Wireshark issue open in a Safari window doesn't cause the CPU issue. Having a docs.gitlab.com page open does. ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Pro tip, at least for Safari users - do not keep GitLab windows open and un-minimized any longer than necessary
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 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 > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Pro tip, at least for Safari users - do not keep GitLab windows open and un-minimized any longer than necessary
On Aug 25, 2020, at 11:42 PM, Guy Harris 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. This appears to be a "feature" of docs.gitlab.com; I currently have a window open to my Wireshark mirror, and it's not eating the CPU, but if I de-minimize the window I have open for setting up mirroring (which I *really* hope I got right and I *really* hope does what I infer it does), the CPU lights up. ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Pro tip, at least for Safari users - do not keep GitLab windows open and un-minimized any longer than necessary
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 Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
