Support request: MallocStackLogging: can't turn off malloc stack logging because it was not enabled

[dmorand17]

Checks

• I ran cw doctor in the affected command line session and it didn't resolve my issue
• I ran cw restart and it didn't resolve my issue
• I searched the discussions in this repo and there are no duplicates of my issue

Expected behaviour

I am using autocomplete for aws commands (i.e. aws cloudformation ) and sporadically receive errors about MallocStackLogging

Actual behaviour

When using cw in ZSH I'm getting sporadic issues where autocomplete fails with the following error.

MallocStackLogging: can't turn off malloc stack logging because it was not enabled

Steps to reproduce

No response

Environment

CODEWHISPERER-details:
  - 0.14.1
hardware-info:
  - model: 
  - model-id: 
  - chip-id: Apple M1
  - cores: 8
  - mem: 16.00 GB
os-info:
  - macOS 14.3.1 (23D60)
environment:
  - shell: /bin/zsh
  - terminal: vscode
  - cwd: /Users/domorand/workspace/work/_research-computing/open-on-demand-on-aws
  - exe-path: /Users/domorand/.local/bin/cw
  - install-method: unknown
  - env-vars:
    - CWTERM_SESSION_ID: 8fdd2794947248378c13baf3d2793a33
    - CW_SET_PARENT_CHECK: 1
    - CW_TERM: 0.14.1
    - PATH: /Users/domorand/.local/bin:/opt/homebrew/bin:/opt/homebrew/opt/gnu-sed/libexec/gnubin:/opt/homebrew/opt/coreutils/libexec/gnubin:/Users/domorand/.nvm/versions/node/v20.11.0/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/Users/domorand/.zplug/repos/zplug/zplug/bin:/Users/domorand/.zplug/bin:/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:/Users/domorand/.cargo/bin:/Users/domorand/.local/bin:/opt/homebrew/opt/fzf/bin:/Users/domorand/workspace/personal/scripts/aws/lambda:/Users/domorand/workspace/automated-security-helper:/Users/domorand/workspace/personal/scripts/aws/iam:/Users/domorand/.guard/bin
    - SHELL: /bin/zsh
    - TERM: xterm-256color
    - ZDOTDIR: /Users/domorand
    - __CFBundleIdentifier: com.microsoft.VSCode
    - CW_SET_PARENT: 8fdd2794947248378c13baf3d2793a33

[wang-zhenqi]

I ran into this issue too. Done the cw doctor and cw restart, but the message keeps showing up.

Environment

CODEWHISPERER-details:
  - 0.15.1
hardware-info:
  - model:
  - model-id:
  - chip-id: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  - cores: 6
  - mem: 16.00 GB
os-info:
  - macOS 14.4.0 (23E214)
environment:
  - shell: /bin/zsh
  - terminal: iterm
  - cwd: /Users/zhenqi.wang
  - exe-path: /Users/zhenqi.wang/.local/bin/cw
  - install-method: brew
  - env-vars:
    - CWTERM_SESSION_ID: 0549bbbf484e4ca197936ca63c7fd3a5
    - CW_SET_PARENT_CHECK: 1
    - CW_TERM: 0.15.1
    - DISPLAY: /private/tmp/com.apple.launchd.YXHgKkDVUX/org.xquartz:0
    - PATH: /Users/zhenqi.wang/opt/anaconda3/bin:/Users/zhenqi.wang/.asdf/shims:/usr/local/opt/asdf/libexec/bin:/Users/zhenqi.wang/opt/anaconda3/bin:/Users/zhenqi.wang/.sdkman/candidates/java/current/bin:/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/TeX/texbin:/usr/local/munki:/Users/zhenqi.wang/.local/bin
    - SHELL: /bin/zsh
    - TERM: linux
    - __CFBundleIdentifier: com.googlecode.iterm2
    - CW_SET_PARENT: 0549bbbf484e4ca197936ca63c7fd3a5

[doreilly257]

me too:

CODEWHISPERER-details:

• 0.15.1
  hardware-info:
• model:
• model-id:
• chip-id: Apple M2
• cores: 8
• mem: 8.00 GB
  os-info:
• macOS 14.3.1 (23D60)
  environment:
• shell: /bin/zsh
• terminal: iterm
• cwd: /Users/doreilly/Work/AI/search
• exe-path: /Users/doreilly/.local/bin/cw
• install-method: unknown
• env-vars:
  • CWTERM_SESSION_ID: 839e3e1a56ea4e6ead61ad8ba0fe46bd
  • CW_SET_PARENT_CHECK: 1
  • CW_TERM: 0.15.1
  • PATH: /Users/doreilly/Library/pnpm:/Users/doreilly/.warpstream:/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:/Library/TeX/texbin:/Users/doreilly/.cargo/bin:/Users/doreilly/.local/bin:/Users/doreilly/.local/bin:/Users/doreilly/.local/bin:/opt/homebrew/opt/fzf/bin
  • SHELL: /bin/zsh
  • TERM: xterm-256color
  • __CFBundleIdentifier: com.googlecode.iterm2
  • CW_SET_PARENT: 839e3e1a56ea4e6ead61ad8ba0fe46bd

[geoffreywiseman]

I have seen similar reports for Fig repo and CodeWhisperer, so ... suggests this issue is long-standing?
https://github.com/withfig/fig/actions/runs/5975421320
aws/q-command-line-discussions#121

[grant0417]

Yes, we have investigated these issues but have yet to find any solution.

[pricklywiggles]

Same here. This is making me have to restart Q at least once a day.

[grant0417]

We have tried to release a fix for this in the 1.4.0 release, if you still run into this issue please let us know. Otherwise we will assume this is resolved and close this ticket in a few weeks.

[geoffreywiseman]

This is happening a lot lately for me and I'm on 1.4.5. It had been a bit since I'd seen it, so I thought it was fixed, but ... now it's back. Maybe a regression?

[geoffreywiseman]

This is happening to me so frequently that I may just uninstall at this point -- it's a nice feature, but lately it's causing more pain than it's helping? May try again if this gets fixed, but it's just brutal lately. This is a command I ran a few minutes back:

[slkh]

I have the same issue as well, also on a mac. Sometimes I have to restart the whole terminal which is quite annoying.

[ciandt-crodrigues]

Issue still happens, and very often on macos

[kunaljubce]

Issue continues to happen, this is a little frustrating.

[seaders]

This issue had disappeared for me for at least a month, but reoccurred about a week ago and is now happening in nearly every console window. It's now worse than it ever was with fig and q.

Here's what's now showing from a brand new console tab, during a brew install