lensapp / lens

Lens - The way the world runs Kubernetes
https://k8slens.dev/
MIT License
22.59k stars 1.47k forks source link

Lens Helper keep running after I quit Lens #866

Open oreza opened 4 years ago

oreza commented 4 years ago

Describe the bug I see that bunch of Lense Helper are running on my Mac OSx catalina even though there is no instance of Lense running on my system.

PID TT STAT TIME COMMAND 89236 ?? S 0:54.86 /Applications/Lens.app/Contents/Frameworks/Lens Helper (GPU).app/Contents/MacOS/Lens Helper (GPU) --type=gpu-process --field-trial-handle=1718379636,12830367575625659745,11435127973942017941,131072 --disable-features=LayoutNG,SpareRendererForSi PID TT STAT TIME COMMAND 89662 ?? S 3:34.48 /Applications/Lens.app/Contents/Frameworks/Lens Helper (Renderer).app/Contents/MacOS/Lens Helper (Renderer) --type=renderer --field-trial-handle=1718379636,12830367575625659745,11435127973942017941,131072 --disable-features=LayoutNG,SpareRender PID TT STAT TIME COMMAND 89695 ?? S 20:09.72 /Applications/Lens.app/Contents/Frameworks/Lens Helper (Renderer).app/Contents/MacOS/Lens Helper (Renderer) --type=renderer --field-trial-handle=1718379636,12830367575625659745,11435127973942017941,131072 --disable-features=LayoutNG,SpareRender

I have not ran Lense for almost 3 weeks.

It seems like Lense is using kubectl proxy to access the api, and that is spawning Helpers, that are just hogging the processor.

To Reproduce Steps to reproduce the behavior:

  1. Start Lense
  2. Quit Lense
  3. Start terminal
  4. ps aux | grep Lens

Expected behavior After I quit Lens, it should shut down all the sub processes.

Screenshots

Screen Shot 2020-09-11 at 4 30 15 PM

Environment (please complete the following information):

Additional context If you have osquery installed, and are wondering what are these unnamed processes you can run it

osqueryi "SELECT pid, name, path FROM processes where name='';" | grep -Eo '[0-9]{1,5}' | while read -r line ; do ps $line; done
Nokel81 commented 3 years ago

Is this still a problem?