Include thread name in Memray live tracking view

[gibsondan]

Include thread name in Memray live tracking view

[pablogsal]

Thanks for opening an issue @gibsondan!

We do have the thread name already collected so it should be fairly simple to pass it through the layers and display it in the TUI

[godlygeek]

Each thread has a string name

Can you clarify which string name you're referring to, @gibsondan ?

[gibsondan]

@godlygeek when you create a thread in python, you can supply a name: https://docs.python.org/3/library/threading.html#thread-objects

(Or a threadpoolexecutor can specify a prefix which is applied to all threads created in that pool)

I don't know offhand how that is translated into the operating system internals but I suspect it's through something like this: https://man7.org/linux/man-pages/man3/pthread_setname_np.3.html

py-spy, for example, includes these names in its output via commands like py-spy dump or the flamegraph produced by py-spy record:

Thread 41 (idle): "schedule_daemon_worker_7"

[godlygeek]

We do have access to the name set through pthread_setname_np, but we don't have access to the name set using threading.Thread.name, and setting the name on a Python Thread object doesn't automatically cause pthread_setname_np to be called with the same name (or even a leading prefix of it).

That said, it would be interesting to try to collect the name attribute set on a threading.Thread... I wonder if we're able to...