Keybase is killing my battery

Not sure what's going on, but Keybase seems to be consuming a lot of energy according to OS X's Activity Monitor. Is this expected at this point in development? Sent some logs if they are useful in troubleshooting this: a1b2ad5ee2e84a1fbe97a01c

Some screenshares:

and then...

Maybe related, but when I Quit Keybase.app from the menubar there are still some keybase processes hanging around.

Before quitting:

❯ ps aux | grep -i keybase
crcastle        29616  22.8  1.0  3329068  84964   ??  S     2:41PM   0:02.98 /Applications/Keybase.app/Contents/Frameworks/Keybase Helper.app/Contents/MacOS/Keybase Helper --type=renderer --no-sandbox --lang=en-US --node-integration=true --num-raster-threads=2 --enable-zero-copy --content-image-texture-target=3553,3553,3553,3553,3553,34037,3553,3553,3553,34037,3553,34037,34037 --video-image-texture-target=34037 --channel=29612.1.804710486
crcastle        29614  10.5  0.3  2718484  27360   ??  S     2:41PM   0:01.20 /Applications/Keybase.app/Contents/Frameworks/Keybase Helper.app/Contents/MacOS/Keybase Helper --type=gpu-process --channel=29612.0.1497789292 --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=14,15,29,34,38,47,51,58,64 --gpu-vendor-id=0x8086 --gpu-device-id=0x162b --gpu-driver-vendor --gpu-driver-version
crcastle        29612   9.3  0.9  3420768  74916   ??  S     2:41PM   0:01.78 /Applications/Keybase.app/Contents/MacOS/Electron
crcastle        29617   0.1  1.1  3345660  96124   ??  S     2:41PM   0:01.32 /Applications/Keybase.app/Contents/Frameworks/Keybase Helper.app/Contents/MacOS/Keybase Helper --type=renderer --no-sandbox --lang=en-US --node-integration=true --num-raster-threads=2 --enable-zero-copy --content-image-texture-target=3553,3553,3553,3553,3553,34037,3553,3553,3553,34037,3553,34037,34037 --video-image-texture-target=34037 --channel=29612.2.217889654
crcastle        26035   0.0  1.3 573441920 113160   ??  S     9:09AM   0:02.86 /Applications/Keybase.app/Contents/SharedSupport/bin/kbfs -debug /keybase
crcastle        26015   0.0  0.2 573452052  20512   ??  S     9:08AM   0:02.04 /Applications/Keybase.app/Contents/SharedSupport/bin/keybase -d service
root              775   0.0  0.0  2471628    968   ??  Ss   Thu02PM   0:00.04 /Library/PrivilegedHelperTools/keybase.Helper
crcastle        29846   0.0  0.0  2432792    560 s000  R+    2:41PM   0:00.00 grep --color=auto -i keybase

After quitting:

❯ ps aux | grep -i keybase
crcastle        26035   0.0  1.3 573441920 113160   ??  S     9:09AM   0:02.86 /Applications/Keybase.app/Contents/SharedSupport/bin/kbfs -debug /keybase
crcastle        26015   0.0  0.2 573453100  20588   ??  S     9:08AM   0:02.06 /Applications/Keybase.app/Contents/SharedSupport/bin/keybase -d service
root              775   0.0  0.0  2471628    968   ??  Ss   Thu02PM   0:00.04 /Library/PrivilegedHelperTools/keybase.Helper
crcastle        29883   0.0  0.0  2423572    344 s000  R+    2:43PM   0:00.00 grep --color=auto -i keybase

If I kill these (including sudo kill the root-owned one), then Keybase.app menu bar icon automatically starts up including a bunch of other processes. I assume this has something to do with launchctl or some other watchdog.

Start by reproducing on OS X and comparing the provided ps aux output before and after quitting Keybase.app; investigate the listed keybase, kbfs, and privileged helper processes plus the launchctl/watchdog possibility. Done means quitting the app stops the expected processes without manual kill and avoids the reported high energy use.