If attached log file contains information really related to the problem, it may be a bug in the recording component. Somehow set-dialog-result lose its parameter list and that somehow triggers the dialog "looping". The only question is "how?", it is very unlikely to lose parameters in RecordingAspect or SWTEventRecorder. Even more, I have artificaly recreated this unexpected situation in Q7 interface, section + button + SWT message dialog + no parameters to set-dialog-result sent from RecordingAspect, the test just fails, no looping.
If it is not an SWT MessageDialog, there are some signs it may not (get-window recorded), that may be some problem in event flow simulation. In any case, it is painful to debug such things without access to actual AUT. We need it.