5.2.8.1 update - Crashes BI

Post Reply
MikeBwca
Posts: 488
Joined: Thu Jun 20, 2019 5:39 am

5.2.8.1 update - Crashes BI

Post by MikeBwca » Thu May 21, 2020 10:42 pm

Updated from 5.2.7.12 to 5.2.8.1.

Update notes:
- BVR file metadata for overlay and motion.
- Dual-streaming enhancements.
- Other minor enhancements and bug fixes.

I was excited to start using the BVR file metadata.

When I enabled the overlay for 1 camera, BI crashed.
I started and tried another camera, crashed again.
Tried the original camera, and BI crashed again.

Restored back to 5.2.7.12. Overlays work fine. Probably just me, right? I have such a specific, custom system, that only I will have this issue. :roll:

WmG
Posts: 39
Joined: Sat Jun 29, 2019 7:10 pm

Re: 5.2.8.1 update - Crashes BI

Post by WmG » Fri May 22, 2020 12:11 pm

From 5.2.8.0 to 5.2.8.1. Already had overlays enabled for one camera. Disabled, OK'd, reenabled, OK'd, everything continues to function as expected. Don't have a clue what metadata does so can't comment on that. Happy hunting. W10, 64bit

Edit: Actually read the help file update info and right clicking on the playing video file does display the metadata although (for me on a clip with only camera supplied text) motion overlays were only shown if text overlays was also selected. Very cool though

Matts1984
Posts: 61
Joined: Fri Apr 10, 2020 1:12 pm

Re: 5.2.8.1 update - Crashes BI

Post by Matts1984 » Fri May 22, 2020 1:17 pm

5.2.8.0 was fine for me yesterday (no clue on this metadata thing but I'm just talking about operation).

5.2.8.1 seems to be online but I have a 'Clip: write error 80000456, undefined' on all of my cameras. Rebooted server and errors were still present. I manually cleared them and so far they are gone... I'll check back in a bit to see if it stays that way.

EDIT - It's been about 90 minutes since I manually cleared, new clips have been created, and all still seems to be smooth.
Blue Iris 5.2.9.x | Windows Server 2019 VM | 12GB RAM | Intel Xeon X5650 @ 2.67GHz - 8 Cores | 6TB Local RAID | Sophos UTM WAF

MikeBwca
Posts: 488
Joined: Thu Jun 20, 2019 5:39 am

Re: 5.2.8.1 update - Crashes BI

Post by MikeBwca » Sat May 23, 2020 8:19 am

Thanks for the replies.

I tried 5.2.8.2 update. Same thing. When I enable overlays in the console, BI crashes. I've tries repairing the database, and, starting with a new database.
During playback, the options work fine.


Sent a message to Support.

User avatar
reddawg
Posts: 128
Joined: Sun Jun 30, 2019 11:29 am

Re: 5.2.8.1 update - Crashes BI

Post by reddawg » Sat May 23, 2020 9:50 am

MikeBwca wrote:
Sat May 23, 2020 8:19 am

I tried 5.2.8.2 update. Same thing. When I enable overlays in the console, BI crashes. I've tries repairing the database, and, starting with a new database.
During playback, the options work fine.

Sent a message to Support.
After updating from 5.2.8.0 x64 to 5.2.8.2 x64, Blue Iris console would hang shutting down when I tried to exit the console. This happens whether overlays are enabled or not. I am running BI v5 as a standalone application not as a service. I reverted my version back to 5.2.8.0 x64. I also sent a message to support.

MikeBwca
Posts: 488
Joined: Thu Jun 20, 2019 5:39 am

Re: 5.2.8.1 update - Crashes BI

Post by MikeBwca » Mon May 25, 2020 5:33 am

Has something to do with C:\WINDOWS\System32\ucrtbase.dll

User avatar
reddawg
Posts: 128
Joined: Sun Jun 30, 2019 11:29 am

Re: 5.2.8.1 update - Crashes BI

Post by reddawg » Mon May 25, 2020 6:30 am

MikeBwca wrote:
Mon May 25, 2020 5:33 am
Has something to do with C:\WINDOWS\System32\ucrtbase.dll
Interesting. The update for 5.2.8.3 resolved my problem with Blue Iris hanging when I tried to exit from the console. What did ucrtbase.dll have to do with the problem? I think the DLL you mentioned has something to do with Microsoft Visual C++ Redistributable for Visual Studio.

MikeBwca
Posts: 488
Joined: Thu Jun 20, 2019 5:39 am

Re: 5.2.8.1 update - Crashes BI

Post by MikeBwca » Mon May 25, 2020 1:24 pm

Yes. I've 'repaired' the Microsoft C++ redist 2015-2019, and, ran SFC. Tried another user account. Same issue.

Post Reply