Repro is with GA Zui tagged v1.8.0 and at commit 52b4b58.

A user first reported the issue in a community Slack thread. In their own words:

Can't open any packet after the recent update, I keep getting this error!
Same issue on both Windows and Linux deb

Will try that but everything works fine except when I double click a packet. I created a new pool then loaded the pcap file then query after that when I double click on a packet, I get that error

I seem to have reproduced the issue on macOS as well, though I'd word the repro a little differently than the user. The problem doesn't seem to be "packet" specific, but rather, I was able to trigger it by applying fuse and then opening a record in the Detail view. Here's a repro in GA Zui tagged v1.8.0 using the attached ifconfig.pcapng.gz test data (after uncompressing).

I then did a binary search and confirmed the problem started happening at commit 52b4b58, which is associated with the changes in #3103. This next video is a repro at commit 52b4b58 using the attached results.zng.gz test data, which is just the records generated by loading that ifconfig.pcapng.

Since this shows a more detailed error message I can start digging in and figure out what needs to be fixed. However, a secondary question is why the stack dump shown to the user in the GA release is so opaque. In this case I was lucky to have been able to make a lucky guess as to how to trigger the problem (the many null values in the background of the user's screenshot made me suspicious that fuse was involved) but it would have been much more helpful if the stack trace could have referenced the original lines of code.