4 ms·
It sounds like the camera was sending match results using a blocking send or write call, and no one was reading them, so once the total size of match results ex
by voidmain 7y ago
It sounds like the camera was sending match results using a blocking send or write call, and no one was reading them, so once the total size of match results exceed the total size of socket buffers the camera software blocks and stops working.
- plasma 7y agoDefinitely seen this too. There may be an OS buffer that becomes full (holding data from network but app has not read from OS buffer) so now it’s blocked.
- mokus 7y agoYup, that’s exactly my thought too. I’ve seen this in USB virtual serial port debugging connections too. The software is writing debug messages, nobody reads them, and a day or two later everything just stops because the debug connection’s buffer is full.
- msandford 7y agoThat was what I thought too! I've been bitten by a similar issue where I thought I was dodging it by using a size unlimited Python Queue but the underlying buffer filled up anyhow.
- ohazi 7y agoYou'll run out of memory eventually... an "unlimited size" queue usually just means that the original developer won't be around to deal with the fallout.