Tracking issue for server stability

[raphCode]

Here I collect open issues related to zellij server stability, meaning problems that may cause sessions to crash or become otherwise unuseable. Currently, I limit this list to issues where active work can get lost, e.g. a new session crashing directly at startup is out of scope.

This is the second list, the old one being #1100

Server crashes

• [x] https://github.com/zellij-org/zellij/issues/1532
• [x] https://github.com/zellij-org/zellij/issues/1590
• [ ] https://github.com/zellij-org/zellij/issues/1350
• [ ] https://github.com/zellij-org/zellij/issues/1649
• [ ] https://github.com/zellij-org/zellij/issues/1758
• [x] https://github.com/zellij-org/zellij/issues/1751
• [ ] https://github.com/zellij-org/zellij/issues/1944
• [x] https://github.com/zellij-org/zellij/issues/1949
• [x] https://github.com/zellij-org/zellij/issues/1948
• [ ] https://github.com/zellij-org/zellij/issues/1985
• [x] https://github.com/zellij-org/zellij/issues/1993
• [ ] https://github.com/zellij-org/zellij/issues/2112
• [x] https://github.com/zellij-org/zellij/issues/2329

Inaccessible session / corruption

• [ ] https://github.com/zellij-org/zellij/issues/1063
• [x] https://github.com/zellij-org/zellij/issues/1588
• [ ] https://github.com/zellij-org/zellij/issues/1255

Feel free to ping me in other / new issues if I should update this list.

[fansari]

Hope this will be fixed. It is not so bad as it was in the beginning but I still have to kill zellij and start again because the session is freezing. Then I typically see two times "zellij attach" when running "ps -ef | grep zellij". I kill them and start again - but of course it always takes time to recreate all stuff as it was before. I use version 0.30.0.

https://github.com/zellij-org/zellij/issues/1588

[kabirz]

Had same issue in version 0.31.1

[dougg0k]

Why not put an auto error reporting option that does not collect anything personal?