Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

GTK: Tabs leak CPU memory when closed #5491

Open
mitchellh opened this issue Jan 31, 2025 · 1 comment
Open

GTK: Tabs leak CPU memory when closed #5491

mitchellh opened this issue Jan 31, 2025 · 1 comment
Labels
gui GUI or app issue regardless of platform (i.e. Swift, GTK) os/linux
Milestone
1.1.1

Comments

@mitchellh
Copy link
Contributor

Discussed in #4366

Originally posted by rhodes-b January 1, 2025
This is easy to reproduce, open quite a few tabs (I did 20 new ones in this case) and see that memory is not being recovered when they are closed

@00-kat confirmed this in discord

image

These were my stats

202MB with one tab
275MB 20 tabs
close 20 tabs
235MB with one tab

It may be MiB im not sure what btop uses by default
@mitchellh mitchellh added gui GUI or app issue regardless of platform (i.e. Swift, GTK) os/linux labels Jan 31, 2025
@mitchellh mitchellh added this to the 1.1.1 milestone Jan 31, 2025
@rhodes-b
Copy link

rhodes-b commented Feb 1, 2025

valgrind never worked for me but I could get heaptrack to work

heaptrack.ghostty.zst.txt
(remove .txt extension github would let me upload otherwise)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
gui GUI or app issue regardless of platform (i.e. Swift, GTK) os/linux
Projects
None yet
Milestone
1.1.1
Development

No branches or pull requests
2 participants
@mitchellh @rhodes-b