Vladislav Nepogodin

> SIGTSTP handling is only about "uninstalling" all the terminal hooks previously installed, before the actual SIGTSTP handler. I don't believe it exists any good reasons to disable SIGTSTP handler....

> Hey @vnepogodin would you have answers to my previous comment? I have a question: How can I disable SIGTSTP handling? I guess this one should be enough: https://github.com/ArthurSonzogni/FTXUI/blob/master/src/ftxui/component/screen_interactive.cpp#L427

As far as I can see it should be it Because after it receives SIGTSTP it do "uninstall", and throws SIGTSTP again(idk why it should work like that), and then...

> It sounds like way too much! How big is your terminal dimensions? Are you on Linux? I will take a look and verify how much is needed. was 136...

btw I made it faster a bit, but memory usage is changed 

Update: Memory usage is changed after introducing animation and other cool features I think that virtual memory usage is high because of how `shared_ptr`s works :eyes: 

Yeah I have no problem about that. ``` ==45685== HEAP SUMMARY: ==45685== in use at exit: 0 bytes in 0 blocks ==45685== total heap usage: 39,077 allocs, 39,077 frees, 44,362,563...

> > What if somewhere unwanted references are kept ? > > They would use resident memory, not virtual memory. > > I tried proxying calls to the allocator to...

> Nice! I didn't knew about heaptrack. That's a great discovery! Thanks for taking a look! The temp allocations reduced. but still exist as you can see on the screenshot...

> so it just adds an option but that option aint doing nothin'? By default yes nothing will happen, because by default xwayland is enabled. If you add: ``` xwayland...