Issues like this are usually caused by you running into some
operating-system-imposed limit.
See, for example
http://www.live555.com/liveMedia/faq.html#scalability
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mail
Dear Mr. Ross Finlayson,
We are running Live555 Media Server on a RedHat Linux 6 version. Our
Hardware is Intel Pentium Core2 Duo processor running at 2.93 GHz with 2 GB
RAM.
We are running client application ( openRTSP ) on multiple systems. We are
observing this issue.
We are launching
>Unfortunately the cameras themselves are purchased both by us and resold and
out of band by the customer.
>Some can and are willing to update, others are not even open to it.
>However, if the camera is using the "LIVE555 Streaming Media" software, then -
>under the terms of the LGPL - thei
> First a confession. Every update I modify Boolean.hh. The addition of
> || (defined(_MSC_VER) && _MSC_VER >= 1400)// MSVC++ 8.0, Visual
> Studio 2005 and higher
>
> On line 19 some time ago. always breaks my build.
I made this change in May 2012 because someone noted that "MSVC++ 8.0,
> Unfortunately the cameras themselves are purchased both by us and resold and
> out of band by the customer.
> Some can and are willing to update, others are not even open to it.
However, if the camera is using the "LIVE555 Streaming Media" software, then -
under the terms of the LGPL - their m
I am more than a few lists and can't remember for sure, but was it this list
that asked about possible feature requests after the usage survey?
At the time I couldn't think of any, but todays update reminded me of one.
First a confession. Every update I modify Boolean.hh. The addition of
||
Thank you very much! I will update immediately.
Unfortunately the cameras themselves are purchased both by us and resold and
out of band by the customer.
Some can and are willing to update, others are not even open to it.
This message and any attachments contain confidential and proprietary
> It is ALWAYS immediately follows the error message :
>
>MultiFramedRTPSource error: Hit limit when reading incoming packet over
> TCP. Increase MAX_PACKET_SIZE;
That turned out to be useful information. (It's a pity you didn't mention that
before :-)
> Could it be that by calling brea
I have been trying to solve this issue in my code since before I updated to the
2013.03.07 code.
Inspection always shows the packet having a valid address but the guts of the
packet are tagged with the heap code for destruction.
It is ALWAYS immediately follows the error message :
MultiFrame
