search for: virnetclientstream

...Problem is that instead of returning NULL to >> our malloc()-s once the limit is reached, kernel decides to kill us. >> >> For anybody with libvirt insight: virNetClientIOHandleInput() -> >> virNetClientCallDispatch() -> virNetClientCallDispatchStream() -> >> virNetClientStreamQueuePacket(). >> >> >> The obvious fix would be to stop processing incoming packets if stream has >> "too much" data cached (define "too much"). But this may lead to >> unresponsive client event loop - if the client doesn't pull data from >&g...

...libvirt uses to transfer binary data). Problem is that instead of returning NULL to our malloc()-s once the limit is reached, kernel decides to kill us. For anybody with libvirt insight: virNetClientIOHandleInput() -> virNetClientCallDispatch() -> virNetClientCallDispatchStream() -> virNetClientStreamQueuePacket(). The obvious fix would be to stop processing incoming packets if stream has "too much" data cached (define "too much"). But this may lead to unresponsive client event loop - if the client doesn't pull data from incoming stream fast enough they won't be...