anarcat

and i just tried to reproduce in a *debian* container and I *can't* reproduce. so there's something on my desktop, or environment or *something* that triggers this. i'll also note...

> I build and test, after replacing sync.Mutex with delock.Mutex (build against golang 1.23). Hopefully I'll come back with more info. do you have an actual patch showing what you...

i see this hang with that patch as well. note that i don't even need to have a Puppetfile or any special environment: just running `g10k -version` in an empty...

well, it's interesting. the bug doesn't trigger if you remove everything up to the flag parser and all files but config.go g10k.go and helper.go. i'll keep bisecting like this if...

for what it's worth, i *can't* reproduce this by building g10k with golang 1.19 on debian trixie. so it definitely sounds like a regression somewhere in golang, between 1.19 and...

> strace ./g10k -version that thing is *massive*, mainly a lot of futex failures [g10k-strace.txt](https://github.com/user-attachments/files/18768887/g10k-strace.txt) > ps aux | grep [g]10k ``` USER PID %CPU %MEM VSZ RSS TTY STAT...

oh, and here's a "normal" strace run in a debian unstable container, where the issue is not reproduced. [g10k-strace-normal.txt](https://github.com/user-attachments/files/18768982/g10k-strace-normal.txt)

oh wow. it's a terminal issue. if i run g10k -version inside gnome-terminal, the bug doesn't trigger. but if i run g10k inside foot or alacritty, then the process hangs....

@nickTh-tyn did you see the part where i can't reproduce inside gnome-terminal but i can under foot and alacritty? have you tried reproducing that?

that is the weirdest bug this month.