bug: Fig Graphics and Media consuming over 160 GB of ram

[virgildotcodes]

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

MacOS 14 Sonoma

Expected behaviour

Fig should not use 162 GB of ram.

Actual behaviour

I got an alert from MacOS telling me that I've run out of memory. I check activity monitor and I see "Fig Graphics and Media" sitting there at 162 GB of ram. I just upgraded to Sonoma, and this is my first time noticing the issue. Have not been able to replicate it, but thought I'd note it here regardless.

Steps to reproduce

Not as of yet.

Environment

fig-details:
  - 2.16.0
hardware-info:
  - model:
  - model-id:
  - chip-id: Apple M1 Max
  - cores: 10
  - mem: 32.00 GB
os-info:
  - macOS 14.0.0 (23A344)
environment:
  - shell: /bin/zsh
  - terminal: iterm
  - cwd: /Users/username
  - exe-path: /opt/homebrew/bin/fig
  - install-method: brew
  - env-vars:
    - FIGTERM_SESSION_ID: b3690428-2354-42ee-9b6f-da761b28b118
    - FIG_SET_PARENT_CHECK: 1
    - FIG_TERM: 2.16.0
    - PATH: /Users/username/Library/Application Support/Herd/bin/:/Users/username/.rbenv/shims:/Users/username/.bun/bin:/opt/homebrew/Cellar/pyenv-virtualenv/1.2.1/shims:/Users/username/.pyenv/shims:/Users/username/.nvm/versions/node/v18.17.1/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin:/usr/local/share/dotnet:~/.dotnet/tools:/usr/local/go/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Users/username/.cargo/bin:/Users/username/.fig/bin:/Users/username/.local/bin:/Users/username/Library/Application Support/JetBrains/Toolbox/scripts:/Users/username/.composer/vendor/bin
    - SHELL: /bin/zsh
    - TERM: xterm-256color
    - __CFBundleIdentifier: com.googlecode.iterm2
    - FIG_PID: 31915
    - FIG_SET_PARENT: b3690428-2354-42ee-9b6f-da761b28b118

[realshubhamraut]

lol, This is Crazy usage !! 😯

[goritm]

Having the same issue. Just upgraded to Sonoma yesterday.

[AISLVE]

@goritm are you facing the signups are disabled error when trying to signup, can you please confirm

[tl-Talha-Sheikh]

Similar issue for me. I had 60GB of usage. Is this normal? 😨

[abotellokindalab]

Similar issue here, 33GB of RAM usage! It's unreal! Plus my battery drained quickly and temperature was really high

[ProfJackCZ]

Same issue. After upgrading to Sonoma Fig Graphics and Media takes up more than 20GB of Ram after some time running.

[jamescooked]

Same, was taking up 60GB memory and causing the "your system has run out of application memory" prompts on Sonoma. Sorry Fig but I've had to uninstall until this is sorted

[adrian-mcmichael]

Same, had it reach similar sizes and get the same "your system has run out of application memory" popups. Had to kill the process. Its happening on both macbooks I have with Sonoma on them.

[rejkee]

Same here after upgrading to Sonoma.

[nayeemdev]

Same issue after upgrading to Sonoma.

[alewtschuk]

Just upgraded to Sonoma, also having the same issue 37 GB of ram usage and no more memory popup.

[rohankokkulabp]

After upgrading to Sonoma. ~40 GB of RAM!!??

[paulhuynhdev]

I got a similar issue that cost 12GB of RAM usage!!!

[wolfadex]

I came back to this after stepping away for an hour today. I was at over 68GB of swap used as well.

[jpintoic]

I also noticed this weird behaviour after upgrading to MacOS Sonoma. I only have 8GB of RAM on my M1 Mac but I noticed the computer getting hot for the first time ever and noticed that Fig was consuming almost half of all my RAM:

Also my laptop was making a very faint sound like it was accessing the disk all the time, once I quit fig that also went away.

[guilhermeramos0603]

I have the same problem with my MacBook Air M2 with 16GB of RAM. I felt my Mac warm up, but the problem was resolved when I uninstalled Fig. At first, I thought the problem was related to Xcode 15 or the iOS 17 emulator.

[mschrage]

We are actively investigating this. Thank you for reporting.

[timack]

Also seeing this along with the "your system has run out of application memory" popup.

MacBook Pro. 2.6 GHz 6-Core Intel Core i7. OS 14.0 (23A344). 32 GB 2667 MHz DDR4

[lukepistrol]

Also happening to me on Sonoma on a Mac mini M1

[JulianKingman]

60gb on a 15" M2 MB Air, lmk if I can help somehow. Sounds like a memory leak. Good luck!

[rNNdom]

Also consuming more tha 10gb of ram on mac m1 with 8gb

[bouli]

Same issue here! (M1 / 8GB / SONOMA 14.0)

[hakimmazouz]

Another one here, Sonoma, M1 Macbook Pro 2020 8GB, I kept getting "out of memory" pop-ups on Mac OS but nothing in the list was consuming barely over 500mb.

Checked Activity Monitor and saw 28GB from Fig Graphics & Media

[edenilson-ruiz]

Same issue

[diogohudson]

Thas Nice!! Big Head one! 🧠

Also in SONOMA

[SGLara]

Same here, let us know when there is a fix. Thanks!

[sudomf]

Any update here? Same happening to me on M2 16GB Ram

[KieranConlon]

I'm having the same problem - am also seeing very high CPU usage (varies between 150% to 300%) with the Fig Graphics and Media process. Fig v2.17.0 on macOS v14.0 (Sonoma) with MBP Intel i9

I found that manually running fig restart does give some temporary relief but the high usage does creep up again over time.

[Goooler]

Links #2355, #1208

[freds-dev]

Same issue here.

[daneclarkcollins]

Found this because I have the same issue. Glad to see they're working on it.

[Timothy1102]

I'm also having this issue, the popup "your system has run out of application memory" appears and "Fig graphics and media" takes up 40GB of memory.

system info: macOS Sonoma, M1 chip.

[tommyboy326]

I have to uninstall fig don't know when the issuse can be fix

[geekbrother]

Looks like a classic memory leak issue. Restarting every n hours helping for now.

[virgildotcodes]

Just thought I'd add another, potentially confusing, data point. I'm the OP, and since opening this issue I've had fig running nonstop, and the problem hasn't popped up again - no more memory issues since. Laptop runs for over 8 hours a day, every day, and I've only restarted the laptop once or twice in the last few weeks. I haven't had to specifically restart fig at any point. I didn't consciously do anything to address the issue, so it seems to have fixed itself, at least on my laptop.

[kevinrss01]

I have the same issue here (macbook pro M2 PRO)

[kkxiaoa]

same issues for Sonoma 14.0 in M2 pro.

[xilopaint]

Does this software have a changelog? I'm about to uninstall it. It feels unmaintained.

[Redtama]

Same issue just arose for me a few days after upgrading to Sonoma on an M1 Pro.

[draganjerinic23]

Same issue, 117GB - Sonoma M1 Pro

[PaulMarcel]

Same issue. Sonoma on an Intel iMac. So what does this process do? The system makes thumbnails just fine so I don't see why a terminal utility needs to scan my system to generate thumbnails that already exist. I've forced regenerating thumbnails on my system before and despite all the media, it takes maybe an hour as a low-priority process. Fig G&M takes 40% of my machine, tons of memory, and never stops. So what is it actually doing?

[Redtama]

Just thought I'd add another, potentially confusing, data point. I'm the OP, and since opening this issue I've had fig running nonstop, and the problem hasn't popped up again - no more memory issues since. Laptop runs for over 8 hours a day, every day, and I've only restarted the laptop once or twice in the last few weeks. I haven't had to specifically restart fig at any point. I didn't consciously do anything to address the issue, so it seems to have fixed itself, at least on my laptop.

Same here. After initially having the issue and restarting fig, I've now had it running for a days without the memory usage growing (it's sitting comfortably at ~230MB). So whatever caused the memory usage to spiral out of control has not recurred.

[adam-code-labx]

The issue seems to happen after leaving my machine on over night. Currently have to stop the Fig Graphics and Media process forcefully to free up memory.

[fergusmeiklejohn]

I also have the problem since upgrading to Sonoma. Just crashed my Mac..

[BClev]

Just happened for the first time today. M2 Max, macOS Sonoma (14.1.1)

[wzaldivar]

Happened for the first time today, after being out from keyboard for 4 hours aprox, M2 Pro, Sonoma 14.1.1

[grant0417]

Hey, we just relaunched under AWS as CodeWhisperer, this version should have a lot of the memory leak issues resolved, I would encourage you to give that a try: https://aws.amazon.com/blogs/devops/introducing-amazon-codewhisperer-for-command-line/

[PaulMarcel]

Excellent... looking at the CodeWhisperer page, it doesn't mention Fig at all. The download has us drag CodeWhisperer into the Apps folder. Running it, it didn't disable or uninstall Fig. I quit my shells and then deleted Fig. Things seem to work. Will miss the name Fig, tbh

Le lun. 20 nov. 2023 à 20:53, Grant G @.***> a écrit :

Hey, we just relaunched under AWS as CodeWhisperer, this version should have a lot of the memory leak issues resolved, I would encourage you to give that a try: https://aws.amazon.com/blogs/devops/introducing-amazon-codewhisperer-for-command-line/

— Reply to this email directly, view it on GitHub https://github.com/withfig/fig/issues/2753#issuecomment-1820184061, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFIZJEOC4PYMZELK4EUWJDYFQQSVAVCNFSM6AAAAAA5JV5AM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRQGE4DIMBWGE . You are receiving this because you commented.Message ID: @.***>

--

Paul-Marcel ST-ONGE
Latté Evangelist
HalfInchShy.com A woodworking video podcast and blog!

[agodin3z]

Hey, we just relaunched under AWS as CodeWhisperer, this version should have a lot of the memory leak issues resolved, I would encourage you to give that a try: https://aws.amazon.com/blogs/devops/introducing-amazon-codewhisperer-for-command-line/

Do you know if we can use it with the existing fig account? 🤔

[diogohudson]

Hey, we just relaunched under AWS as CodeWhisperer, this version should have a lot of the memory leak issues resolved, I would encourage you to give that a try: https://aws.amazon.com/blogs/devops/introducing-amazon-codewhisperer-for-command-line/

Do you know if we can use it with the existing fig account? 🤔

I don't thinks this is possible @agodin3z. It is kind forcing us to use a AWS builder account. Look the print inside the app settings:

AWS is not doing a good work on this. There is a typo on the Quit program name, should be CodeWhisperer but they forgot to change the FIG!