Wireshark · Wireshark-dev: Re: [Wireshark-dev] Pro tip, at least for Safari users - do not keep GitLab windows open and un-mini

Wireshark-dev: Re: [Wireshark-dev] Pro tip, at least for Safari users - do not keep GitLab wind

From: Guy Harris <gharris@xxxxxxxxx>

Date: Wed, 26 Aug 2020 00:17:01 -0700

On Aug 25, 2020, at 11:54 PM, Dario Lombardo <lomato@xxxxxxxxx> 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.

References:
- [Wireshark-dev] Pro tip, at least for Safari users - do not keep GitLab windows open and un-minimized any longer than necessary
  - From: Guy Harris
- Re: [Wireshark-dev] Pro tip, at least for Safari users - do not keep GitLab windows open and un-minimized any longer than necessary
  - From: Dario Lombardo

Prev by Date: Re: [Wireshark-dev] Pro tip, at least for Safari users - do not keep GitLab windows open and un-minimized any longer than necessary
Next by Date: Re: [Wireshark-dev] GitLab migration update
Previous by thread: Re: [Wireshark-dev] Pro tip, at least for Safari users - do not keep GitLab windows open and un-minimized any longer than necessary
Next by thread: [Wireshark-dev] Cherry-picking, gitlab permissions
Index(es):
- Date
- Thread