[Greg McKaskle]

The DS UI freeze happens when a synchronous operation inside of an event structure takes much longer than expected, thus blocking the processing of other button clicks and such. Pretty much all of the communication and protocol work takes place in independent/parallel loops that should be unaffected.

The DS released 12/14 experienced this when mDNS was unexpectedly affected by firewall or other protective SW. An operation that normally took 200ms was taking many seconds. So the DS release in 2/15 moved the mDNS call out of the event structure so that a slow return wouldn't affect other UI events. It also printed a message when the slow return is detected.

Apparently, you have discovered something similar. I have never reproduced this or seen it happen at an event, so I don't have good info for debugging it.

Do you think that a particular tab or button or operation is common to when you see it freeze? Does it happen at about the same time as the communications light comes on?

Thanks for any helpful debugging info.
Greg McKaskle