The v2.4.6.0 introduced a 3MB frame-size limit for MJPEG streams, due to problems with some streaming sources having adverse effects on device memory.

Frame-image sizes can vary immensely for video streams and at the higher extreme, memory issues occur which can result in app-crashes etc. Safeguards were implemented in the current build to mitigate this.

The new build currently in review retains a memory limit safeguard, but we are also avoiding displaying the image size warning for streams. Now if a frame-exceeds the limit, it is dropped and the next-frame is processed. What is happening in the current build is the stream is stopped until the refresh period is invoked, hence you can see either interrupted source-video or stopped altogether if you have no refresh defined.