You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The libxcm control interface (libxcm/ctl.c) uses ~38 kb stack, which may cause issues if the calling thread has a tiny stack configured.
It should be possible to peek on the control fd to see if data is available, and in that case do a 38 kb short-lived heap allocation. However this "peeking" should be efficient (as fast as recv() or faster), since the process_client() functions is run often (as long as a client is connected).
The text was updated successfully, but these errors were encountered:
The libxcm control interface (libxcm/ctl.c) uses ~38 kb stack, which may cause issues if the calling thread has a tiny stack configured.
It should be possible to peek on the control fd to see if data is available, and in that case do a 38 kb short-lived heap allocation. However this "peeking" should be efficient (as fast as recv() or faster), since the process_client() functions is run often (as long as a client is connected).
The text was updated successfully, but these errors were encountered: