Anyone else seeing a 100-second freeze of the live stream from a camera after confirmed alerts?

There is an issue that I keep seeing every time I try upgrading to a BI release higher than 5.7.8.3.

On these newer releases (and I’ve tried most of them, including 5.8.9.3) after an AI confirmed alert is logged the alerting camera will often appear to freeze in the BI Console for a period of 99-100 seconds.

In the BI console, the symptoms I see are the Yellow warning triangle appears above the window and the image freezes (both the camera’s date time overlay and the BI date time overlay stop updating). If I make note of the timestamp during the freeze and the timestamp at the point when the image resumes updating, there are always either 99 or 100 seconds between the two timestamps.

If I then play back the alert, I find that the recording actually does include the entire time period that the live view froze. The timestamp from the camera ticks up the entire time, but the BI timestamp freezes for the same 99-100 second period in the recording as I had observed in the live view.

I raised the issue with BI Support about 3 weeks ago, but although Ken has asked me to try the releases since then they have all shown the behavior.

Is anyone else seeing this or similar behavior?

digger11 said:

There is an issue that I keep seeing every time I try upgrading to a BI release higher than 5.7.8.3.

On these newer releases (and I’ve tried most of them, including 5.8.9.3) after an AI confirmed alert is logged the alerting camera will often appear to freeze in the BI Console for a period of 99-100 seconds.

In the BI console, the symptoms I see are the Yellow warning triangle appears above the window and the image freezes (both the camera’s date time overlay and the BI date time overlay stop updating). If I make note of the timestamp during the freeze and the timestamp at the point when the image resumes updating, there are always either 99 or 100 seconds between the two timestamps.

If I then play back the alert, I find that the recording actually does include the entire time period that the live view froze. The timestamp from the camera ticks up the entire time, but the BI timestamp freezes for the same 99-100 second period in the recording as I had observed in the live view.

I raised the issue with BI Support about 3 weeks ago, but although Ken has asked me to try the releases since then they have all shown the behavior.

Is anyone else seeing this or similar behavior?

Click to expand...

that is what is happening to me but I do not have Ai setup, I did but after an update it became flaky so I removed it

Coldair said:

that is what is happening to me but I do not have Ai setup, I did but after an update it became flaky so I removed it

Click to expand...

I would think that this would seem to indicate that the issue isn't specifically with AI confirmed alerts. I haven't run any tests on the latest release with AI disabled, but I suspect I would still see the behavior. When I have AI disabled, motion alerts trigger the "On alert" action defined for the camera. Maybe it has something to do with these actions.

My "On alert" actions use curl to send an API request to Pushover, what do you have in the way of "On alert" actions for the cameras you have seen the problem on?

I don't think this can be attributed to AI settings.

Yesterday I got a reply back from Ken saying that he thinks this has something to do with AI settings, and that he thinks release 5.8.9.5 is going to be highly stable.
After reading the email I went ahead and upgraded to 5.8.9.5.
I didn't see any issues right away, but this morning I could see that the ~100 second freeze in the live console was happening again. Not every alert was showing the symptom, but it was happening pretty regularly.

At 8:36 AM I disabled AI, making no other changes.

Within a few minutes an alert came in on one of my cameras and I saw the yellow Triangle appear above that camera's live view in the console.
When I maximized the window I could see that it was frozen, with both the camera and BI timestamps showing 08:49:12.
I continued to observe that window and it resumed displaying live video at timestamp 08:50:55.

A playback of the recording of that alert with Testing & Tuning > Analyze with motion detector shows that the camera

• Triggered at 08:49:00 (Orange border)
• Trigger ended at 08:49:13 (Border disappeared. At this point the live view in the console was frozen at timestamp 08:49:12)
• BI timestamp stopped incrementing 08:49:15 (Camera timestamp continued incrementing)
• BI timestamp resumed incrementing 08:50:54

I also caught 4 other alerts while AI was disabled that exhibit the same behavior where the timestamp stops updating a second or two after the motion trigger ends,
Three were from the same camera, and another was from a different camera.
SouthWest - Trigger ends at 09:03:44, BI timestamp frozen 09:03:46 - 09:05:25
SouthWest - Trigger ends at 09:16:17, BI timestamp frozen 09:16:19 - 09:17:58
LPCAM2 - Trigger ends at 09:16:33, BI timestamp frozen 09:16:34 - 09:18:13
SouthWest - Trigger ends 09:20:38, BI timestamp frozen 09:20:39 - 09:22:18

Reviewing confirmed alerts from before disabling AI I also see the same behavior. Playback of the clip with 'Analyze with motion detector' enabled shows the motion trigger end a second or two before the BI timestamp stops updating.
Here are just two of several available examples, these chosen because they are from two other cameras.
LPCAM - Trigger ends at 08:24:23, BI timestamp frozen 08:24:24 - 08:26:03
BMP_6MM - Trigger ends at 08:24:24, BI timestamp frozen 08:24:26- 08:26:05

Something that I find interesting is that with AI enabled, I couldn't find any motion alerts that weren't confirmed by AI that exhibited the behavior.
I looked at ~ 15 alerts from the SouthWest cam that came in between 07:00 and 08:30. Although Testing & Tuning showed they were triggered by motion, AI did not confirm any of those events, and no freezes occurred. Within 45 minutes of disabling AI I observed two alerts on that camera where the timestamp stopped updating within 2 seconds of the motion trigger ending.

I have downgraded to 5.7.8.3 and reenabled AI.

while checking event viewer the other day I saw this critical error in the log. I wonder what is causing this