The stack trace is hard to interpret, but it could possibly show the call to hide being in the same call stack as the call to show. It may be necessary to show some of the additional code involving this dialog, so we can see its full life cycle.
Since the dialog cannot be closed by the user, it appears that it must be closed automatically. What triggers the dialog to close (e.g. a window.setTimeout, etc)? If the call to open and hide are too close together (i.e. the call to hide finishes before the call to show finishes), there may be a synchronization issue going on.