Opening syscalls view crashes Sysdig Inspect

Observed behavior

When opening the "Syscalls" view, Sysdig Inspect starts to read the trace file but the UI freezes and all UI elements disappear after processing 16 - 20% of the trace file.

This problem reproduces always with the attached trace file (I did not try others).

Steps to reproduce

1. Open "Sysdig Inspect"
2. Open trace.scap.zip (does not contain any sensitive info; it was captured in a newly created Virtualbox VM)
3. Click on "Syscalls" in the bottom left corner

System info

The trace was captured on:

# uname -a
Linux packer-virtualbox-iso-1512307732 4.4.0-101-generic #124-Ubuntu SMP Fri Nov 10 18:29:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
# sysdig --version
sysdig version 0.8.0

The system running Sysdig Inspect:

# uname -a
Darwin io 15.6.0 Darwin Kernel Version 15.6.0: Mon Oct  2 22:20:08 PDT 2017; root:xnu-3248.71.4~1/RELEASE_X86_64 x86_64
# Sysdig Inspect version
Version 0.2.0 (0.2.0)

Additional info

In the MacOS system log we see the following:

10/12/17 13:16:26,989 diagnosticd[129]: error evaluating process info - pid: 1698, puniqueid: 1698
10/12/17 13:16:27,151 ReportCrash[1643]: Saved crash report for Sysdig Inspect Helper[1698] version 0 to /Users/daniel/Library/Logs/DiagnosticReports/Sysdig Inspect Helper_2017-12-10-131627_io.crash

See more details in the crash report Sysdig Inspect Helper_2017-12-10-131627_io.crash.zip.

Start by reproducing the crash with the attached trace.scap.zip and the Syscalls view, then read the linked macOS crash report and system-log entries for Sysdig Inspect Helper. Done means the trace finishes processing and the UI remains available instead of freezing or disappearing.