Explosive memory and thread leak?

[nihil2501]

Report

No idea what happened here. I was just having a look at btop because it's pretty and I watched these memory and thread stats growing extremely quickly, particularly in these child-less login processes. Something on the order of 1 GiB / second. Apologies if I'm just not understanding what btop was reporting here.

I don't fully remember, but I think I quit Ghostty and reopened it and got it to exhibit this unbounded growth again after opening btop, and then after opening a new tab, the growth started–but my memory might be off here. After that I couldn't repro.

My system didn't feel sluggish during any of this.

System

• OS: macOS Sonoma 14.6 arm64
• Host: MacBook Pro (16-inch, Nov 2023, Three Thunderbolt 4 ports)
• Kernel: Darwin 23.6.0
• Shell: fish 3.7.1
• Terminal: ghostty 1.0.1
• CPU: Apple M3 Pro (12) @ 4.06 GHz
• GPU: Apple M3 Pro (18) @ 1.38 GHz [Integrated]

[jmckillican]

anything showing up in your system logs in Applications > Utilities > Console.app?

[nihil2501]

anything showing up in your system logs in Applications > Utilities > Console.app?

I just looked for the pids in my screenshot and nothing interesting stands out there. Also no diagnostic reports from the event in question, though I do see that it generated 3x cpu_resource.diags on 1.0.0 (e.g. 100% average CPU usage over 90s).

This is the first time I've seen Console.app. Is there anything you suggest I look for? I have the pids and timestamp of the event.

[mitchellh]

I haven't seen other reports of this, but would obviously want to fix this. To get there, we need to figure out what's causing it. Any tips on reproducing for me would be excellent.

[nihil2501]

Goodness gracious, it looks like this is a display bug of btop:

• Infinite memory usage glitch. (Display bug, not a btop memory leak).
• [BUG] MemB and Threads keeps rising after collapsing a process in tree mode.

Apologies @mitchellh. Loving this terminal!

[jmckillican]

man that bug is funny if it is the same one, if it happens again I'd look at activity monitor and make sure since the MemB memory usage bug is just a display one in btop and not the actual system.

[goonzoid]

I've been able to reproduce this, and agree that it very much seems like a btop bug:

Here's btop right now:

And then Activity Monitor for the same process:

[c02y]

I got similar bug when running programs like btop and nvtop, it takes around 2GB memory

Archlinux + i3wm here.