zsh (figterm)(7164) MallocStackLogging: can't turn off malloc stack logging because it was not enabled.

RamiroG8k commented 1 year ago

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.0.0 (23A5286i)

Expected behaviour

I was expecting just to have yarn write down but this message happen to appear just suddenly

Actual behaviour

https://github.com/withfig/fig/assets/66712961/5655db5a-9c1f-41e1-a49b-e58d700902fd

Steps to reproduce

actually just writing yarn [SOMETHING]

or as in the video.. just cd .

Environment

fig-details:
  - 2.16.0
hardware-info:
  - model: 
  - model-id: 
  - chip-id: Apple M2
  - cores: 8
  - mem: 8.00 GB
os-info:
  - macOS 14.0.0 (23A5286i)
environment:
  - shell: /opt/homebrew/Cellar/zsh/5.9/bin/zsh
  - terminal: vscode
  - cwd: /Users/ramg8k/100Ladrillos/web-app
  - exe-path: /opt/homebrew/bin/fig
  - install-method: brew
  - env-vars:
    - DISPLAY: /private/tmp/com.apple.launchd.XMywiEJhwz/org.xquartz:0
    - FIGTERM_SESSION_ID: 39b265f7-0d9f-4ddc-a47d-06a54c77676a
    - FIG_PID: 4721
    - FIG_SET_PARENT: 39b265f7-0d9f-4ddc-a47d-06a54c77676a
    - FIG_SET_PARENT_CHECK: 1
    - FIG_TERM: 2.16.0
    - PATH: /Users/ramg8k/Library/pnpm:/Users/ramg8k/.rbenv/shims:/Users/ramg8k/.rbenv/shims:/Users/ramg8k/.rbenv/bin:/Users/ramg8k/.nvm/versions/node/v18.16.0/bin:/Users/ramg8k/.nvm/versions/node/v18.16.0/bin:/Users/ramg8k/.pyenv/shims:/Users/ramg8k/.pyenv/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:/opt/X11/bin:/Library/Apple/usr/bin:/Users/ramg8k/Library/pnpm:/Users/ramg8k/.rbenv/shims:/Users/ramg8k/.rbenv/bin:/Users/ramg8k/.nvm/versions/node/v18.16.0/bin:/Users/ramg8k/.pyenv/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/Users/ramg8k/.fig/bin:/Users/ramg8k/.local/bin
    - SHELL: /bin/zsh
    - TERM: xterm-256color
    - ZDOTDIR: /Users/ramg8k
    - __CFBundleIdentifier: com.microsoft.VSCode

OfficialCRUGG commented 1 year ago

Same problem with pnpm. With cd it spams the message like a couple hundred times even. My terminal is unusable like this.

TBetcha commented 1 year ago

I was running a dotnet project and started seeing this issue as well.

RamiroG8k commented 1 year ago

For me the current solution is to kill the current terminal tab or open another one and run fig restart

samdenty commented 1 year ago

getting this as well

Coffeegerm commented 1 year ago

Getting the same thing and it looks like fig restart clears up the error.

Sirjoseph94 commented 1 year ago

Even after fig restart I am still getting the same error.

zsh (figterm)(51179) MallocStackLogging: can't turn off malloc stack logging because it was not enabled.

punctuations commented 1 year ago

getting the same issue and the only solution I've found is killing the terminal session and running fig restart

KoshiFutami commented 12 months ago

I had the same problem and tried killing the session and running fig restart, but the error kept happening again and again. The best solution for me was to uninstall and install the app again. I've never run into the same error since then, maybe for one week!

skravetz-binternacional commented 11 months ago

same here :( error persists when doing fig restart, but if i open a new terminal it disappears

sh (figterm)(31065) MallocStackLogging: can't turn off malloc stack logging because it was not enabled.

budimanr3101 commented 11 months ago

just exit your terminal and open again..... and it will be fix 🚀

ravindarreddy1 commented 11 months ago

same for me too

OscarVanL commented 11 months ago

Same error here. It's super frustrating.

jacsamell commented 11 months ago

Same here, this is impossible to work with, disabling Fig until this is fixed

ntilva commented 11 months ago

Same for me as well

Tjerk-Haaye-Henricus commented 11 months ago

same here

budimanr3101 commented 11 months ago

same for me too

just exit your terminal and open again..... and it will be fix 🚀

Upendrasengar commented 9 months ago

same for me too

just exit your terminal and open again..... and it will be fix 🚀

Restarting your terminal is temporary, I don't prefer to restart everytime.

claudiusraphael commented 9 months ago

Still present in Sonoma 14.3. Since not only fig suffers from it, but also neovide for example when using the terminal in it, the culprit seems to be in either Apples implementation of zsh or since the same behavior can be reproduced by doing a simple brew upgrade in the zsh (assuming you use brew) - only that in this case ruby is the bad guy - all points to macOS Sonoma as the origin in general. Not an issue in Ventura, nor Monterey.

kmorwood commented 9 months ago

I waited a long time to try fig (or whatever it is called now)...and this issue popped up within 10 minutes.

...back to waiting for fig...

Apostolos-Daniel commented 8 months ago

I'm seeing this issue too on version 2.17.1 and using vscode zsh terminal. Any idea of a permanent fix? Closing the terminal and starting a new one does indeed fix the issue temporarily but it does come back.