Open Grimille opened 10 months ago
I can confirm i have the same issue.
I can confirm I'm having the same issue as well on my Mac Mini M1
Hi @softwaredeveloptam @joshfedo @Grimille! Thanks for reporting. The team is investigating why this memory leak is limited to Fig and doesn't impact CodeWhisperer.
If you only use autocomplete (and not Scripts, Dotfiles, Servers), try using Amazon CodeWhisperer for CLI. You'll get effectively the same autocomplete experience, minus these performance issues.
@mschrage i have the same experience with scripts and Dotfiles so it's not just autocomplete.
same memory issue here. using fig 2.17.1 and got an OS X alert saying my system is out of memory. I killed iterm and then noticed that the fig process is trying to use 35GB of RAM (OS X Sonoma 14.3.1 on a M1 13" MBP).
This has been going on for some time...if I forget to check on the fig process it and/or restart it, it'll memory leak into oblivion
Also having the same issue. I'm using Fig 2.17.1 on a MacBook Air M1 with 8 GB of RAM and running macOS Sonoma 14.3.1
Same issue here! Running on MacOS Ventura 13, M2, 16GB of RAM
Checks
fig doctor
in the affected terminal sessionfig restart
and replicated the issue againOperating system
macOS Sonoma 14.1.2
Expected behaviour
Fig is taking a huge amount of memory, filling up RAM and Swap Partition to maximum and causing macOS instability.
Actual behaviour
Steps to reproduce
It was the first time it happened.
I didn't turn off my Mac Studio for 3 days. I didn't replicate the issue yet.
Environment