Dialog Enqueue Multiple Files with encode running became unresponsive | VidCoder 8.26 on Windows 10

[JNavas2]

What were you doing when VidCoder crashed?

With an encode running, I attempted to Enqueue Multiple Files. The dialog opened on the desired folder with about 20 video and corresponding SRT files. I changed the View to Group by Type, then attempted to select multiple video files whereupon VidCoder became unresponsive. I waited, and the encode completed successfully but the queue did not get updated and VidCoder remained unresponsive. I eventually killed VidCoder with Task Manager. I have both mini and full dumps if you want them. Crash detail is the Exception Analysis from the mini dump.

OS Name Microsoft Windows 10 Pro Version 10.0.19045 Build 19045 System Manufacturer LENOVO System Type x64-based PC Processor Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz, 2904 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date LENOVO R0FET60W (1.40 ), 05/26/2023 Installed Physical Memory (RAM) 32.0 GB

Crash details

This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(3628.d40): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtWaitForMultipleObjects+0x14:
00007ffc`a124dbb4 c3              ret
0:034> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

Failed to request MethodData, not in JIT code range

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 5436

    Key  : Analysis.Elapsed.mSec
    Value: 21588

    Key  : Analysis.IO.Other.Mb
    Value: 36

    Key  : Analysis.IO.Read.Mb
    Value: 18

    Key  : Analysis.IO.Write.Mb
    Value: 84

    Key  : Analysis.Init.CPU.mSec
    Value: 2030

    Key  : Analysis.Init.Elapsed.mSec
    Value: 52035

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 174

    Key  : CLR.Engine
    Value: CORECLR

    Key  : CLR.Version
    Value: 6.0.1523.11507

    Key  : Failure.Bucket
    Value: NULL_POINTER_READ_c0000005_hb.dll!Unknown

    Key  : Failure.Hash
    Value: {bab657af-b9cb-b578-1d34-e6b19664e589}

    Key  : Timeline.Process.Start.DeltaSec
    Value: 7304

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.Process.Version
    Value: 8.25.0.0

FILE_IN_CAB:  VidCoderWorker.exe.13864.dmp

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)
rax=000000000000b9c2 rbx=000001f3a08a5ac0 rcx=000000000000b9bf
rdx=00000000000755bf rsi=000001f3a087dbb8 rdi=0000000000000000
rip=00000000712b2046 rsp=000000ad8d67f750 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=000001f3e3d1c1f0 r12=000001f3d68f66a0 r13=000001f3a26d7580
r14=000001f3a08a5ac0 r15=000001f3a26d7580
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
hb!ZN4x26511RateControl18rateEstimateQscaleEPNS_5FrameEPNS_16RateControlEntryE+0x196:
00000000`712b2046 498b0a          mov     rcx,qword ptr [r10] ds:00000000`00000000=????????????????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00000000712b2046 (hb!ZN4x26511RateControl18rateEstimateQscaleEPNS_5FrameEPNS_16RateControlEntryE+0x0000000000000196)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

PROCESS_NAME:  VidCoderWorker.exe

READ_ADDRESS:  0000000000000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

STACK_TEXT:  
000000ad`8d67f750 00000000`712b3edd     : 00000000`00000000 00000000`00000000 000001f3`a087dbb8 000001f3`d68f66a0 : hb!ZN4x26511RateControl18rateEstimateQscaleEPNS_5FrameEPNS_16RateControlEntryE+0x196
000000ad`8d67f890 00000000`71246949     : 000001f3`a08808f0 000001f3`d6b976a0 00000000`00000fc0 000001f3`a0869e80 : hb!ZN4x26511RateControl16rateControlStartEPNS_5FrameEPNS_16RateControlEntryEPNS_7EncoderE+0x48d
000000ad`8d67f950 00000000`7124a468     : 000001f3`a087dad0 00000000`00000000 00000000`00000000 00000000`00000ba8 : hb!ZN4x26512FrameEncoder13compressFrameEv+0x4d9
000000ad`8d67fb10 00000000`712f15ba     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hb!ZN4x26512FrameEncoder10threadMainEv+0x1a8
000000ad`8d67fb70 00007ffc`9ff17604     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hb!ZN4x26514TemporalFilter17destroyRefPicInfoEPNS_24TemporalFilterRefPicInfoE+0x9a
000000ad`8d67fba0 00007ffc`a12026a1     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
000000ad`8d67fbd0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

SYMBOL_NAME:  hb+196

MODULE_NAME: hb

IMAGE_NAME:  hb.dll

STACK_COMMAND:  ~34s; .ecxr ; kb

FAILURE_BUCKET_ID:  NULL_POINTER_READ_c0000005_hb.dll!Unknown

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {bab657af-b9cb-b578-1d34-e6b19664e589}

Followup:     MachineOwner
---------

[RandomEngy]

This is the most useful unmanaged crash report I've gotten since I started this project in 2010. It's even got a stack trace!

Looks like this crashed inside hb.dll. This stack may be of interest to the HandBrake team.

[JNavas2]

This is the most useful unmanaged crash report I've gotten since I started this project in 2010. It's even got a stack trace!

Thank you. As a developer myself I know how frustrating it can be to get a report like "It stopped working!" with no further details, so I do try to make my own reports as useful as possible. I've not been able to reproduce the problem, so it may have just been a rare combination of events.