error while writting, im getting this error : zsh (qterm)(16532) MallocStackLogging: can't turn off malloc stack logging because it was not enabled. zsh (qterm)(16533) MallocStackLogging: can't turn off malloc stack logging because it was not enabled.

[raebeb]

Checks

• I ran q doctor in the affected command line session and it didn't resolve my issue
• I ran q 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

type and get the suggestions in the drop menu

Actual behaviour

every time I'm trying to run any command (git, docker, python, etc) im getting this as I type
zsh (qterm)(16532) MallocStackLogging: can't turn off malloc stack logging because it was not enabled. zsh (qterm)(16533) MallocStackLogging: can't turn off malloc stack logging because it was not enabled.
sometimes work fine and show me the drop menu with the suggestions but after an update of iTerm I started getting this

Steps to reproduce

No response

Environment

[q-details]
version = "1.1.0"
hash = "2f25b08ac0b3bd197c00d0e323ec32126a6c0226"
date = "2024-05-21T20:22:19.598303Z (3d ago)"

[system-info]
os = "macOS 14.5.0 (23F79)"
chip = "Apple M2"
total-cores = 8
memory = "8.00 GB"

[environment]
cwd = "/Users/USER/Dev/mbai-pm-core"
cli-path = "/Users/USER/.local/bin/q"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "iTerm 2"
install-method = "unknown"

[env-vars]
PATH = "/Users/USER/anaconda3/envs/MontBlancAi_venv/bin:/Users/USER/anaconda3/condabin:/opt/homebrew/opt/postgresql@15/bin:/usr/local/opt/postgresql@15/bin:/usr/local/opt/postgresql@15/bin:/Library/Frameworks/Python.framework/Versions/3.12/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/Library/Frameworks/Python.framework/Versions/3.11/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:/Applications/iTerm.app/Contents/Resources/utilities:/Users/USER/.local/bin"
QTERM_SESSION_ID = "d73d72989c7946228fa9b6ed4991207d"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.1.0"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.googlecode.iterm2"

[grant0417]

This is a known issue that some users have ran into, we are not sure what is the cause and is currently not reproducible for us.

[macsir]

I am on 1.4.0 but still have this issue appearing from time to time.

[rossng]

This still happens to me in 1.4.5

[alissonph]

Im facing the same problem. Version 1.4.5

[handlerda]

This is still occuring

[OneHIve-Africa]

This still occurs

[Rheannone]

Experienced this randomly today. Running q doctor and q restart seems to have resolved it for now.

[natuan62]

I have same isssue with iterm2

[BATspock]

Facing the same issue. q restart resolved it for now. Q version : q 1.9.1

[pararang]

facing this issue in ghostty + zsh, fixed it by updating the oh-my-zsh

[YuriyShestakov]

It's not updating, it is resolved temporarily when you restart the terminal, and the omz update restarts it. I usually fix it using the "Restart" mouse right click popup command in iterm2. The next day, or sometimes in several days, it appears again.
I wonder, why their team just did not remove the disabling MallocStackLogging command from the code. And they can't do that FOR YEARS? It seems like a pretty straightforward fix - just remove the command that disables the memory leak logging, so it won't yield that error again.
Actually, if it is enabled, I don't care. As well as if it is disabled, I don't have any memory leak debuggers so I think this logging won't appear anywhere.
Maybe this command comes from some dependency libraries? Or the malloc logging is managed somehow automatically by OS so it starts/stops automatically when a memory leak is detected and we can do nothing with it and need to raise a ticket to Apple? Or it's just some XCode build command checkbox and developers forget to turn it off when building for production?
If we know more information from the Q (fig) team investigations about this long-standing problem for the past 5 years, I think the whole society will help to fix the issue.
Otherwise, all people eventually will stop using q in favor of other modern tools appearing nowadays.

[YuriyShestakov]

I had this error, if I am not mistaken, since version 0.8 or similar, when I finally switched from bash to zsh / oh-my-zsh. Also, I have powerlevel10k installed, if it is related. And everything is in iterm2.
I have not installed XCode, however, I have Xcode Command Line Tools. Plus, a lot of utilities installed using brew on top of it.
The issue happens only when some time passes, sometimes just a few hours after opening a new panel, sometimes a day or more. I remember once it was working without issues for several weeks.
Also, I always have many tabs / split terms (10-20, up to projects I work on), and when Q breaks in 90% all tabs are broken the same way at the same time. However, restarting one tab (one panel) fixes only that panel.
I passed through many versions of macOS during this time, and 3 different MacBooks, all of them were on Intel CPU. The issue happened on all of them. I did not do a clean install, always just transferring my data to a new laptop.
Ah, almost forgot, it always happens after you write a command and Q tries to display a visual popup, with list of ssh hosts or a list of folders, it does not happen for usual inlined text autocomplete. Also, it does not happen for popups that are visual but with command autocomplete, such as 'omz plugin', etc.

As the problem happens only for a part of users, some of these points may lead to it, and can help to investigate.
Please, do something with this problem, it's really annoying.