Open merkleID opened 2 years ago
Hey @merkleID! Can you share a screen recording of the performance with Fig and then another one without Fig?
Another thing that would be useful is having some data on CPU usage with/without fig, even if that's just the graph in Activity Monitor. Sounds like it's pretty reproducible for you.
Hey @merkleID! Next time this happens can you please quit the Fig app and see if the performance improves?
Hey, I just got your email about asking what and how made my mac slower.
These are why I deleted the app.
mdworker_shared
process are produced and occupy a big capacity of CPU.I am not sure all those symptoms are coming from fig app but I can say that those are all gone after deleting the app.
That’s exactly what happens to me.
I was taking about arrays of command completion directory listing indexes filling up, but I think it’s pretty much the same.
Sometimes it slows down the whole computer, sometimes it’s super fast.
Luca
On 4 May 2022, at 08:31, Lucas Kim @.***> wrote:
Hey, I just got your email about asking what and how made my mac slower.
These are why I deleted the app.
Sometimes multiple mdworker_shared process are produced and occupy a big capacity of CPU. Global search on VS Code got really slow. Gets lag every now and then. I am not sure all those symptoms are coming from fig app but I can say that those are all gone after deleting the app.
— Reply to this email directly, view it on GitHub https://github.com/withfig/fig/issues/1369#issuecomment-1116972350, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHGWR4VVQ5NQXXYFNG7NXL3VIIKT7ANCNFSM5UI7XM2Q. You are receiving this because you were mentioned.
Using fish
on macOS 12.5ß3 and had very similar trouble. fig
was chewing enormous amounts of CPU cycles. Ran for two days, brought my fully loaded MacBookPro18,2 to its knees.
Had over 15 bash processes running for some reason with commands like /bin/bash -lic fc -ln 1
, /bin/bash -lic alias
, /bin/bash --norc --noprofile
and they were all using considerable CPU cycles. Uninstalled and system returned to normal with no bash
processes executing.
This is over a year old but I'm just experiencing. I've been using Fig for a while now, like several months, and love it, but in the past 2 weeks or so, starting a new terminal window takes forever, and I wonder if the culprit is fig.
You had asked for a video of this happening, so here's one: (file to big to share on gh) https://drive.google.com/file/d/14yljFyGa3a6NfFNpEs7Eb6OoV8YyI8e-/view?usp=sharing
First part is with fig closed, albeit other terminals with it running, and then I open fig and open another terminal, and the slowdown on the terminal is pretty similar imo. Again, this JUST started happening to me, before that it worked like a charm 🤷🏻♂️
Thanks for all you do
I've been using fig in my M1 mac for first few it was very great tbh one best terminal out there but after some time makes my mac so slow. once i disable the terminal everything works smooth again.
Having the same issue, where fig_desktop
is the top CPU consumer on my M1 Macbook Pro.
❯ fig doctor
✔ Everything looks good!
Fig still not working? Run fig issue to let us know!
Or, email us at hello@fig.io!
❯ ls /Applications | grep Fig
├── Fig.app
├── Figma.app
❯ where fig
/Users/dramos/.fig/bin/fig
/Users/dramos/.local/bin/fig
/opt/homebrew/bin/fig
/opt/homebrew/bin/fig
same problem on my m1. anyway we can help to debug?
Sanity checks
fig doctor
in the affected terminal sessionIssue Details
As discussed via mail with Brendan, I don't know why but figs slows my imac 4,2ghz/8cores/64RAM and my macbook pro 2.8/8core/16RAM down a lot.
typing into iterm becomes slow, sloppy, slightly unresponsive, and also the whole system becomes slow. this happens on both my macs.
I cleaned .zshrc from any fig-related strings, closed fig.app, and they suddenly woke back up, iterm is super-responsive again.
in my iterm, I use ohmyzsh+powerlevel10k (but currently it's not the theme I am using) I also constantly run ObjectiveSee tools BlockBlock and Lulu. Other tools: AltTab, Magnet
I haven't seen any ram over-use
Also, I just noticed that 'fig diagnostic' reports BASH as being my env shell, while if I type 'env' I get this result:
❯ env [...] SHELL=/bin/zsh [...]
Environment