Docker CUBE OS 2.14.1: Camera streams stop working after multiple views (memory usage normal)

[Alexey_S]

Hello!

I am reporting a persistent issue with camera streams in eWeLink CUBE OS.

Environment:

• CUBE OS version: 2.14.1 (Docker deployment on a PC).
• Hardware: Intel i5, 4 GB RAM.
• Connected devices: 2 eWeLink cameras.
• Current memory usage: 53% (approx. 2 GB out of 4 GB) — so memory is NOT exhausted.

Issue:
After viewing the camera feeds several times, the video stops displaying. The stream will not start again until I manually restart the Docker container. Running sudo docker restart cubeos temporarily fixes it, but the problem returns after a few viewings.

What I have already tried:

• Updated CUBE OS to the latest version (2.14.1) — did not help.
• Verified that cameras work stably in VLC and other applications (so the cameras and network are fine).
• Confirmed H.264 codec and ONVIF/RTSP are enabled.
• Restarted the container — temporary fix only.

Expected behavior: Camera streams should continue to work reliably after multiple views.
Actual behavior: After several open/close cycles, the stream stops starting.

Since memory usage is only 53%, this looks like a software bug (memory leak or resource release issue) in the Docker version of CUBE OS, specifically in the video streaming module.

Request:

1. Confirm if this is a known issue for Docker deployments.
2. Provide a workaround if possible.
3. Let me know if you need any additional logs.

[Jojkoba]

I have reported this same error multiple times; they found one cause and fixed it, but they haven’t fixed the other one yet. So, the problem persists. I had to connect all the cameras to Hik-Connect.

[Miao]

Thank you for your feedback. We apologize for the inconvenience.
To help us locate the issue as quickly as possible, could you please provide the following information?

1. When repeatedly opening/closing the cameras, are you doing so in the same browser tab, or do you have multiple CUBE OS tabs open at the same time?
2. After closing the camera each time, do you reopen it immediately, or after a few seconds or even minutes? Roughly how many operations before the issue occurs?
3. Are the two cameras played simultaneously or separately? After the issue occurs, is it one camera that cannot play, or both?
4. What exactly is the failure: does the playing video suddenly freeze/go gray, or does it fail to load when you reopen it after closing?
5. After the issue occurs, does refreshing the browser page, closing other tabs, waiting a while, and reopening restore playback? Or do you have to restart Docker?
6. Could you reproduce the issue? If so, please provide the exact time the failure occurred (including time zone) and the CUBE OS logs, and send the log file to me via forum private message.
7. You reported that memory usage is 53% of the total 4GB, but camera playback uses Docker /dev/shm shared memory, which is usually only 64MB. If possible, please confirm the shared memory usage when the issue occurs.

To check Docker shared memory usage, refer to the following commands:
Run on the PC host:
(Note: replace cubeos with the actual Docker container name or ID you are using.)

sudo docker inspect cubeos \
  --format 'ShmSize={{.HostConfig.ShmSize}} bytes'

sudo docker exec cubeos df -h /dev/shm

sudo docker exec cubeos \
  ls -lah /dev/shm

Thank you for your understanding and cooperation.

[Alexey_S]

Hello, thank you for the reply.

1. I open one camera in the same tab.

2. It makes no difference whether it happens immediately or after a few minutes; it stops opening after 3–6 operations.

3. I do not launch two cameras simultaneously.

4. Upon the next attempt to open it (see screenshot)…

5. It only recovers after a restart.

6. I have sent the logs via private message.

7. Screenshot attached.

   
   

[Miao]

Hello both,
@Alexey_S @Jojkoba The above issues have been fixed in CUBE OS 2.15.0. Please update to the latest version. The Docker version will be released tonight.