[CrashManager] ValueError: invalid literal for int() with base 10 in CrashInfo.py

Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
<--- TRACEBACK TRIMMED--->
  File "/home/worker/grizzly-auto-run/grizzly/grizzly/session.py", line 155, in report_result
    self.reporter.submit(result_logs, self.iomanager.tests)
  File "/home/worker/grizzly-auto-run/grizzly/grizzly/common/reporter.py", line 254, in submit
    self._submit(report, test_cases)
  File "/home/worker/grizzly-auto-run/grizzly/grizzly/common/reporter.py", line 415, in _submit
    crash_info = self.create_crash_info(report, self.target_binary)
  File "/home/worker/grizzly-auto-run/grizzly/grizzly/common/reporter.py", line 350, in create_crash_info
    auxCrashData=aux_data)
  File "/home/worker/grizzly-auto-run/FuzzManager/FTB/Signatures/CrashInfo.py", line 233, in fromRawCrashData
    result = MinidumpCrashInfo(stdout, stderr, configuration, auxCrashData)
  File "/home/worker/grizzly-auto-run/FuzzManager/FTB/Signatures/CrashInfo.py", line 1328, in __init__
    crashThread = int(components[3])
ValueError: invalid literal for int() with base 10: ''

Start at FTB/Signatures/CrashInfo.py line 1328 and trace the MinidumpCrashInfo input passed from grizzly/common/reporter.py. Inspect the components value that produces an empty string, then exercise the reported CrashManager path and confirm it no longer raises this ValueError for the affected crash data.