Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

Crash after writing a video with x264vfw codec and viewing it or using a clipboard

Highlighted

Environment:
Windows 8.1
LabVIEW 2018 SP1 f4
Vision Development Module 2018-2019 SP1

 

Steps to Reproduce:

  1. Download and install x264vfw codec (as part of K-Lite Mega Codec Pack or standalone);
  2. Create a new VI (or see attached);
  3. Create 2+ videos using this codec:
    1. Drop IMAQ AVI2 Create VI on a BD;
    2. Create a constant for Codec terminal with value x264vfw - H.264/MPEG-4 AVC codec;
  4. Write at least 1 frame into every video using IMAQ AVI2 Write Frame VI;
  5. Close all videos using IMAQ AVI2 Close VI;
  6. Run the VI;
  7. Play any video with external player or copy something into a clipboard.

Expected Result:

LabVIEW continues to work without errors.

 

Actual Result:

LabVIEW crashes with error code 0xC0000005 Access violation:

 

Crash 0x00000000: Crash caught by NIER
File Unknown(0) : Crash 0x00000000: Crash caught by NIER
minidump id: 21ffbb36-1d6e-457f-93d0-11d49208da42
ExceptionCode: 0xC0000005

</DEBUG_OUTPUT>
0x00007FF898A7169C - nierInterface <unknown> + 0
0x00007FF898A76B41 - nierInterface <unknown> + 0
0x00007FF898A75A95 - nierInterface <unknown> + 0
0x00007FF8C1995E71 - mscoreei <unknown> + 0
0x00007FF8CDB1D9B6 - KERNELBASE <unknown> + 0
0x00007FF8D05CC969 - ntdll <unknown> + 0
0x00007FF8D059C910 - ntdll <unknown> + 0
0x00007FF8D059D82D - ntdll <unknown> + 0
0x00007FF8D054916B - ntdll <unknown> + 0
0x00007FF8D059C9EE - ntdll <unknown> + 0
0x000000005ECB9F40 - <unknown> <unknown> + 0
0x00007FF8D034882F - USER32 <unknown> + 0
0x00007FF8D0348618 - USER32 <unknown> + 0
0x00007FF8D034854B - USER32 <unknown> + 0
0x00007FF8D0332434 - USER32 <unknown> + 0
0x00007FF8D0333FE2 - USER32 <unknown> + 0
0x00007FF8D033409D - USER32 <unknown> + 0
0x00007FF8D059C99F - ntdll <unknown> + 0
0x00007FF8D0332F7A - USER32 <unknown> + 0
0x00007FF8D0337BD3 - USER32 <unknown> + 0
0x00007FF8D0337B7F - USER32 <unknown> + 0
0x00007FF66B0336FB - LabVIEW <unknown> + 0
0x00007FF66B163F6A - LabVIEW <unknown> + 0
0x00007FF66B14636B - LabVIEW <unknown> + 0
0x00007FF66B141A5F - LabVIEW <unknown> + 0
0x00007FF89878BE5C - mgcore_SH_18_0 <unknown> + 0
0x00007FF8D00F16AD - KERNEL32 <unknown> + 0
0x00007FF8D0574629 - ntdll <unknown> + 0

 

With VDM 2018 SP1 this issue occurred even with a single video.

 

It seems like the codec gets unloaded before all of its instances are de-initialized.

If you set codec log level to Warning or higher it will display a log window for each codec instance. After closing all videos one of these windows also closes, but the others don't. If you try to switch to these windows LabVIEW will crash as well.

With VDM 2018 SP1 all the log windows stay open, so none of the codec instances are de-initialized.

 

The codec is the latest version. There are no other reports of codec crashes with 0xC0000005 code. There were no codec or Windows updates. The only update was VDM 2018 SP1 to VDM 2019 SP1.

Considering the behavior changed it definitely has something to do with codec handling in VDM.

 

Reported to NI with SR #7810303.

0 Kudos
Message 1 of 1
(123 Views)