Just worked out why mine didn't crash.
I can set full 4K for the group and it works fine when I have 1 4K camera setup. The moment I add the second 4K camera, then I get the problems.
When it is just a single camera in a group, Blue Iris does not treat it as a group, so the resolution is actually being limited to 1280x720.
I just don't understand why we can get Youtube, Netflix etc in 4K, I can live view my cameras directly (hikvision) in IE and get 4K, but not much better than HD in Blue Iris and UI3.
I've tried to explain this before, but it isn't easy to do in non-technical terms. Modern web browsers have good video playback capability, but it is only exposed through a few high level methods and none of those methods is suitable for UI3.
The method used by Youtube, Netflix, etc was designed for working with static files in very specific formats. Live streaming with this method is only possible with several seconds of delay. Blue Iris and UI3 actually support this to some extent (right click on a live stream and choose to open the HLS player) but you'll notice how long it takes to start up a new stream, and notice how delayed it is, and hopefully realize why this isn't the primary streaming method.
You may have also noticed some audio/video calling websites that achieve low delay via a technology called "WebRTC". This could theoretically work for us, however it would require Blue Iris to implement a WebRTC client, which would be an enormous undertaking and I just don't see that happening.
So in order to have the low video delay required for a responsive interface, I had to cobble together a video player that decodes and renders the video stream using JavaScript. I tried every JavaScript-ported video decoder I could get my hands on, but the best I found was only 40% of the speed of a "native" decoder built into a browser. And it crashes if fed 4K video, though I think that is just an issue with the way it was "compiled" rather than a bug in the code. I didn't compile it so I can't easily fix it right now.