Note to RMerlin....Just received a close notice for this issue from Thomas. He went with my original fix of changing the default delay (although smaller, he went with 50ms instead of my 100ms.) I've validated the smaller value is good.
You may want to change to this fix instead of the DELAY_MSEARCH_RESPONSE compile option you picked up in beta2. I actually saw a single hit of the problem in about 2 weeks when running with the compile option (since it's a random delay generation, it likely eventually picked a really small number to cause the single event).
I got the notice too (I'm subscribed to his repo). I'll switch to the upstream fix before the 376.44 release.