RTSP Issues in recent builds

[jbeuree]

I'm currently on 1.35.21, and have had the same problem for a while in the 35 rel. Wondering if I should be using the 35 release or if I should downgrade, and how difficult that may be.

My Foscam with an RTSP stream using ffmpeg has lots of issues, almost as if it can no longer decode the video stream. zmc seems to crash often:
03/13/21 20:07:02.475683 zmc_m5[9053].ERR-zm_signal.cpp/49 [Got signal 11 (Segmentation fault), crashing]
03/13/21 20:07:02.475710 zmc_m5[9053].ERR-zm_signal.cpp/79 [Signal address is 0x7f94ae9a8000, from 0x7f94bfb27efe]
03/13/21 20:07:02.475807 zmc_m5[9053].ERR-zm_signal.cpp/100 [Backtrace 0: /usr/bin/zmc(+0xa0a18) [0x555b2be52a18]]
03/13/21 20:07:02.475814 zmc_m5[9053].ERR-zm_signal.cpp/100 [Backtrace 1: /lib/x86_64-linux-gnu/libpthread.so.0(+0x12980) [0x7f94c33e1980]]
03/13/21 20:07:02.475819 zmc_m5[9053].ERR-zm_signal.cpp/100 [Backtrace 2: /lib/x86_64-linux-gnu/libc.so.6(+0x16eefe) [0x7f94bfb27efe]]
03/13/21 20:07:02.475823 zmc_m5[9053].ERR-zm_signal.cpp/100 [Backtrace 3: /usr/bin/zmc(+0x30f3e) [0x555b2bde2f3e]]
03/13/21 20:07:02.475828 zmc_m5[9053].ERR-zm_signal.cpp/100 [Backtrace 4: /usr/bin/zmc(+0x410f2) [0x555b2bdf30f2]]
03/13/21 20:07:02.475832 zmc_m5[9053].ERR-zm_signal.cpp/100 [Backtrace 5: /usr/bin/zmc(+0x14078) [0x555b2bdc6078]]
03/13/21 20:07:02.475835 zmc_m5[9053].ERR-zm_signal.cpp/100 [Backtrace 6: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f94bf9dabf7]]
03/13/21 20:07:02.475840 zmc_m5[9053].ERR-zm_signal.cpp/100 [Backtrace 7: /usr/bin/zmc(+0x1676a) [0x555b2bdc876a]]

If I try looking at the video, it often is broken about 2/3rd of the way down the image, with just an odd black with white rectangles in the bottom part (screen cap of image attached). Viewing the same stream using vlc is fine with no image issues, which makes me believe it's something to do with zoneminder (plus it started after a previous upgrade).

[Magic919]

It’s the development version. Stay away if you don’t want it broken from time to time. 1.35.16 was ok.

[jbeuree]

Thanks, that's what I expected. Wasn't sure if this was something known to be broken but I'll probably just downgrade for now.

[Magic919]

For current status, you’d need to get in the Slack channel and have a read. They are very busy at the moment, so plenty of builds being pushed out.

I’d say staying off the bleeding edge is a good plan at the minute.