Sometimes I accidentally make a test that never finishes and uses all the CPU and memory available. Killing that manually can be impossible, because switching focus to the right terminal requires more CPU and memory than the kernel can spare.
Signed-off-by: Lars Wirzenius liw@liw.fi
fix: make reading child output not block forever, if there is none
Spawn a thread that sleeps until timeout, then notifies the RealtimeLines condition variable, which wakes up the reader thread and lets it eventually finish.
Signed-off-by: Lars Wirzenius liw@liw.fi
Sometimes I accidentally make a test that never finishes and uses all the CPU and memory available. Killing that manually can be impossible, because switching focus to the right terminal requires more CPU and memory than the kernel can spare.
Signed-off-by: Lars Wirzenius liw@liw.fi
fix: make reading child output not block forever, if there is none
Spawn a thread that sleeps until timeout, then notifies the RealtimeLines condition variable, which wakes up the reader thread and lets it eventually finish.
Signed-off-by: Lars Wirzenius liw@liw.fi