Montage Review scrolling time lag that increases over time
Posted: Wed Feb 22, 2017 3:50 pm
Hi - I'm fairly new to ZM, but not Ubuntu. I've tuned ZM so that it is working quite well, except for the Montage Review feature. It's a bit odd. I have two cameras recording 5fps of 1280x720, Mocord mode. I can run it for a day without any warning or error log messages. When I bring up Montage Review, the behavior changes the longer that ZM has been running (or at least that's what appears to be happening).
If I have just restarted ZM, and bring up MR, select "8 hr", then the scroll works as I would expect (scroll bar (scrubber?) time matches the time in the cameras).
However, If I fire up Montage Review after ZM has been running for a half day or so, then the scroll isn't 'accurate' - i.e. the scroll bar time may be way off compared to the timestamp on the camera. The longer ZM has been running, the greater this gap appears to be. In extremes, the scroll bar time will span 8 hours however the actual timestamp on the camera will only span a few seconds (i.e. when the scroll bar is dragged all the way to the left I only see a second or two change on the cameras' image timestamps, but a full 8 hours on the scrollbar time) . I hope that makes sense. See attached example image.
When I bring up Montage Review I get a backtrace, but I get the same backtrace regardless of whether or not I scrolling acts as expected or has the lag issue.
Any help is appreciated!
System: ZM 1.30.0, Ubuntu 16.04 LTS, 6GB RAM, 1TB 7200RPM HDD and SSD, E5700 CPU @ 3GHz. The system is tuned so that the CPU load stays at around 20%, no memory issues, no swap issues, no CPU temp issues (all monitored via Zabbix).
Backtrace:
If I have just restarted ZM, and bring up MR, select "8 hr", then the scroll works as I would expect (scroll bar (scrubber?) time matches the time in the cameras).
However, If I fire up Montage Review after ZM has been running for a half day or so, then the scroll isn't 'accurate' - i.e. the scroll bar time may be way off compared to the timestamp on the camera. The longer ZM has been running, the greater this gap appears to be. In extremes, the scroll bar time will span 8 hours however the actual timestamp on the camera will only span a few seconds (i.e. when the scroll bar is dragged all the way to the left I only see a second or two change on the cameras' image timestamps, but a full 8 hours on the scrollbar time) . I hope that makes sense. See attached example image.
When I bring up Montage Review I get a backtrace, but I get the same backtrace regardless of whether or not I scrolling acts as expected or has the lag issue.
Any help is appreciated!
System: ZM 1.30.0, Ubuntu 16.04 LTS, 6GB RAM, 1TB 7200RPM HDD and SSD, E5700 CPU @ 3GHz. The system is tuned so that the CPU load stays at around 20%, no memory issues, no swap issues, no CPU temp issues (all monitored via Zabbix).
Backtrace:
Code: Select all
2017-02-22 07:33:14.489478 zms 20567 ERR Backtrace 6: /usr/lib/zoneminder/cgi-bin/nph-zms(+0x167f9) [0x800fe7f9] zm_signal.cpp 102
2017-02-22 07:33:14.484895 zms 20567 ERR Backtrace 5: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf7) [0xb56c6637] zm_signal.cpp 102
2017-02-22 07:33:14.480219 zms 20567 ERR Backtrace 4: /usr/lib/zoneminder/cgi-bin/nph-zms(main+0xb4e) [0x800fd7fe] zm_signal.cpp 102
2017-02-22 07:33:14.475644 zms 20567 ERR Backtrace 3: /usr/lib/zoneminder/cgi-bin/nph-zms(_ZN13MonitorStream9runStreamEv+0xb01) [0x80138b21] zm_signal.cpp 102
2017-02-22 07:33:14.470950 zms 20567 ERR Backtrace 2: /usr/lib/zoneminder/cgi-bin/nph-zms(_ZN7Monitor11SingleImageEi+0x46) [0x80137ee6] zm_signal.cpp 102
2017-02-22 07:33:14.466397 zms 20567 ERR Backtrace 1: [0xb76e1c20] zm_signal.cpp 102
2017-02-22 07:33:14.461492 zms 20567 ERR Backtrace 0: /usr/lib/zoneminder/cgi-bin/nph-zms(_Z14zm_die_handleriP9siginfo_tPv+0x73) [0x8017fee3] zm_signal.cpp 102
2017-02-22 07:33:14.456612 zms 20567 ERR Signal address is 0x4, from 0x80137ee6 zm_signal.cpp 81
2017-02-22 07:33:14.451841 zms 20567 ERR Got signal 11 (Segmentation fault), crashing zm_signal.cpp 50
2017-02-22 07:33:14.447286 zms 20567 ERR Got empty memory map file size 0, is the zmc process for this monitor running?