bug: Fig eating 2GB of memory....

[temrb]

Checks

• [X] I have searched github.com/withfig/fig/issues and there are no duplicates of my issue
• [X] I have run fig doctor in the affected terminal session
• [X] I have run fig restart and replicated the issue again

Operating system

Mac OS M1 Pro

Expected behaviour

Literally stop hogging memory.

Actual behaviour

I had opened an issue regarding the same behaviour way back... #1461 but the issue has gotten worse.

I have uninstalled fig.

Steps to reproduce

Use fig with VSCODE.

1461

Environment

#1461

[ouwargui]

Happened to me too, had to restart my computer, because restarting Fig didn't help.

[SimFG]

eat my 8.6G !!!

[kitsunde]

Fig eats up 10GB+ on my mac even after disabling auto-complete. No idea why but my terminal is practically unusable when fig is running now.

[yidongw]

Fig is eating 1.87GB memory in my M1 Pro, which is insane.

[mschrage]

Potentially related #2576

[o-az]

I have this issue as well. Restarting helps for a few hours then back to very high memory usage.

[cruzluna]

I got one better...26.88 gb. Executing fig settings autocomplete.history.disableLoading true and restarting fig seemed to lowered it to 45 mb. I will update this comment if the memory explodes in size again.

[ScripterSugar]

when fig eating big memory it becomes slow & sluggish as well, and break my terminal experience. I'm opting out from fig as this is not getting fixed and I don't want to restart my mac periodically just to get fig working.

[SimFG]

@ScripterSugar a temp solution: https://github.com/withfig/fig/issues/2584#issuecomment-1595068473

[ScripterSugar]

@SimFG Thank you for sharing, but it seems like that does not solve the fundamental issue I guess. Even with that option disabled, after running my mac without restarting for more than a week fig again started to taking up more than 6gb of memory, so I removed it from my machine and now setting up the alternatives.

[temrb]

i forgot this is still open. to solve the issue, I uninstalled btw. I think there is some memory leak that bogs the crap out of performance. After uninstalling everything returned to normal

[Ansix1207]

Author

i have a same issue , i want fix this memory leak. Can you explain about btw?

[temrb]

i just uninstalled completly and stopped using fig. sticking to zsh if i need autocomplete

[chaynabors]

Can anyone reproduce this after executing fig settings autocomplete.history.disableLoading true and either restarting fig or their machine? This would help tremendously to know one way or the other since the team can't reproduce this locally.

[renkosteenbeek]

Can anyone reproduce this after executing fig settings autocomplete.history.disableLoading true and either restarting fig or their machine? This would help tremendously to know one way or the other since the team can't reproduce this locally.

Sure. I just ran these commands. I will share the results in a day or two.

fig settings autocomplete.history.disableLoading true fig restart

[o-az]

Can anyone reproduce this after executing fig settings autocomplete.history.disableLoading true and either restarting fig or their machine? This would help tremendously to know one way or the other since the team can't reproduce this locally.

Sure. I just ran these commands. I will share the results in a day or two.

fig settings autocomplete.history.disableLoading true fig restart

done. I'll report back in a few days.

[tomgreenhill]

I followed the above advice a while back, but memory usage crept back up to 2.2gb with a week or two. Not sure if there are any other tweaks or solutions to try?

[tixastronauta]

waiting for a fix. until then i have uninstalled fig :(

[mplaul]

Had the same issue a month ago with 5GB memory usage, restarted Fig, went down to <100Mb. Seems like it has crept back up to 6GB this time.

M1 Pro on Monterey, iTerm2 (multiple tabs)

[jasverix]

I just had to kill Fig, it used 14GB memory and made my Mac completely unusable 😅

I am very fond of Fig, but if this is not solved, I cannot continue using it.

[jasverix]

Is there anything we can do to help you figure this out?

I have Fig without any plugins. Mac M2 Pro. Am using JetBrains IDE's with integration with Fig. Am using iTerm2, and working a lot in the terminal, with multiple tabs, and also Terminal in JetBrains IDE's, so there are multiple histories possibly.

Don't know if I have any more relevant info, or if there is any dump og logs etc I can provide. After restart, Fig is working fine, but I suspect it will fill up again in some weeks.

[tomgreenhill]

Is there anything we can do to help you figure this out?

I have Fig without any plugins. Mac M2 Pro. Am using JetBrains IDE's with integration with Fig. Am using iTerm2, and working a lot in the terminal, with multiple tabs, and also Terminal in JetBrains IDE's, so there are multiple histories possibly.

Don't know if I have any more relevant info, or if there is any dump og logs etc I can provide. After restart, Fig is working fine, but I suspect it will fill up again in some weeks.

Likewise, would also love to assist in helping to narrow down the cause as I miss using Fig!

[o-az]

Can anyone reproduce this after executing fig settings autocomplete.history.disableLoading true and either restarting fig or their machine? This would help tremendously to know one way or the other since the team can't reproduce this locally.

Sure. I just ran these commands. I will share the results in a day or two. fig settings autocomplete.history.disableLoading true fig restart

done. I'll report back in a few days.

so far not looking good

[renkosteenbeek]

Can anyone reproduce this after executing fig settings autocomplete.history.disableLoading true and either restarting fig or their machine? This would help tremendously to know one way or the other since the team can't reproduce this locally.

That's after two days of work. I'm using terminal a couple of times per hour.

[o-az]

Can anyone reproduce this after executing fig settings autocomplete.history.disableLoading true and either restarting fig or their machine? This would help tremendously to know one way or the other since the team can't reproduce this locally.

5 days later seeing no difference.

[renkosteenbeek]

Since the root cause seems hard to find, how about an auto restart every hour? That’s better then the current situation.

[vinepb]

M1 Air, happened a couple of times, last time during sleep/suspension.

[ouwargui]

It's happening again right now:

[github-actions[bot]]

This issue has been automatically closed because there has been no activity for 14 days.

[o-az]

This issue has been automatically closed because there has been no activity for 14 days.

that's not true ^_^

[exodia0x]

I have same issue on "Mac Air M1". I'm using fig settings autocomplete.history.disableLoading true already but still eating a lot of ram in few day running

[ScripterSugar]

This issue should be re-opened as it is one of most significant flaw fig has and preventing many people from using fig.

[ofermisk]

reopen! 1.5 gb ram usage is insane

[glennjacobs]

Mine was at 4.93GB - crazy amount and caused my computer to complain.

[SasClaudiuCristian]

FIG Graphics and Media 68 GB today, i was prompt to force quit apps each second, might be probably because of the laptop running 4 days, anyway uninstalling it for sure! m1 macbook pro

[MooseSaeed]

Any updates here?

[btnalexandre]

Same here. Fig take 2Gb on a Macbook Pro 2020 M1...

[o-az]

Any updates on this?

[jimmyn]

Any updates? I have the same issue

[cruzluna]

Any updates? I have the same issue

The founder on X said to install the new released version that is powered by AWS.

X Reply from Falk

[adampatterson]

I have version 2.17.0 and was using 2.3 GB of ram.

Is Fig now code whisperer? I am super confused.

[igr]

And I just wanted to give them money 🤷‍♂️

You know what they say: one fig restart per day, frees a lot of memory away.

killall fig_desktop

[chaynabors]

The team realizes that this is a significant issue for a lot of people on the old app but there's very little we can do to change this right now. My advice is to try CodeWhisperer for the command line which is a much better version of autocomplete (Think Fig with 6+ months of improvements). Since we're now under AWS, our mindset has changed from "move-fast, break everything" to "make what everyone already likes extremely stable and supported".

Download here: https://docs.aws.amazon.com/codewhisperer/latest/userguide/command-line-getting-started-installing.html

This product is in preview, it's still changing and we're always listening to our community. We LOVE feedback, and I promise that even if the team isn't responding, the five of us sync on what everyone wants weekly to isolate all the levers we can pull to make this something people really want to use.

For feedback and long term support you can go here: https://github.com/aws/codewhisperer-command-line-discussions

[adampatterson]

@chaynabors Thanks!

[igr]

@chaynabors thanx. you need to communicate this better on your website. atm it looks like fig is part of the codewhisperer, but that it has life on its own. that is not the case if i have understood correctly. i am happy for fig evolution, but please mind the users. don't go amazon on us.