the dialog is just there to show why the testtool crashes. It afterwards
rethrows the exception (which leads to the crash)

I Assume that the problem also resides in the URP bridge code

or maybe AB can fix it in BASIC itself

So forst assigning to AB

ab->gh: Sorry, but I don't understand what I could do in Basic to fix 
this. During runtime Basic usually catches all Exceptions including
RuntimeException and Exception. So obviously this happens in code
where not all exceptions are caught. Then I need at least a good de-
scription or better a stack.

Besides this: Even if Basic catched this exception what can it do
besides mapping it to an error message and stop working. That's the
same as the testtool application does. I think the problem is that
the "Unexpected connection closure" exception is thrown at all.
Who should take care of something like this, e.g. by trying to re-
connect, if not the testtool application? Basic doesn't even know
if it is used inside the testtool or inside an Office.

TestTool doesn't crash anymore with fixed issue 73372 in OOo,
but I would have loved, that TestTool won't crash, when such an error occures.

It doesn't seem that there would be a general solution for this in the future;
closing

*** This issue has been marked as a duplicate of 73372 ***

.