For whatever reason, fRequestBuffer gets set to a very large number
(i.e. greater than 10K), which causes this function to crash with an
access violation.
It would be nice to figure out what this "whatever reason" actually
is, because it's better to fix a bug than paper over it. However,
I'v
On Tue, Jun 15, 2010 at 2:55 AM, Ross Finlayson wrote:
> I've now installed a new version (2010.06.15) of the code that completely
> removes the "blockUntilReadable()" function. This means that "readSocket()"
> no longer calls "select()", which
> should improve the performance of both client and
I've now installed a new version (2010.06.15) of the code that
completely removes the "blockUntilReadable()" function. This means
that "readSocket()" no longer calls "select()", which
should improve the performance of both client and server applications.
On a related note, here's one other h
On Sun, Jun 13, 2010 at 7:16 PM, Ross Finlayson wrote:
I.e., you should be able to remove the following code from the
> implementation of "readSocket()" in "groupsock/GroupsockHelper.cpp" (line
> 265):
>
>int result = blockUntilReadable(env, socket, timeout);
>if (timeout != NULL && result
Under load, I'm noticing our RTSP server occasionally hangs in this location:
static int blockUntilReadable(UsageEnvironment& env,
int socket, struct timeval* timeout) {
int result = -1;
do {
fd_set rd_set;
FD_ZERO(&rd_set);
if (socket < 0) break;
FD_SET((uns
Hi,
I am a just a beginner in video. I want to play the video data received over IP
(rtp packets) encoded by h264. I have a file in which the rtp packets have been
dumped and I want to play it by vlc player, using live555 server.
I have searched the mailing list and people have worked upon str
Under load, I'm noticing our RTSP server occasionally hangs in this
location:
static int blockUntilReadable(UsageEnvironment& env,
int socket, struct timeval* timeout) {
int result = -1;
do {
fd_set rd_set;
FD_ZERO(&rd_set);
if (socket < 0) break;
FD_SET((unsi
