Andrew Z wrote:
Thanks for the core tip: I didn't think of it. In fact, I did get a
core with the following backtrace, so I should file a bug report in OOo?
Yes, please file an issue (you can assign it to me, sb), and please
include the detailed description of how to reproduce it.
Thanks,
-Stephan
#0 0xb7597e20 in uno_type_isAssignableFromData () from
/opt/openoffice.org2.0/program/libuno_cppu.so.3
#1 0xb759b9a8 in uno_type_isAssignableFromData () from
/opt/openoffice.org2.0/program/libuno_cppu.so.3
#2 0xb75a30b7 in uno_type_any_assign () from
/opt/openoffice.org2.0/program/libuno_cppu.so.3
#3 0xb4280f45 in component_getFactory () from
/opt/openoffice.org2.0/program/acceptor.uno.so
#4 0xb27eb22a in component_getFactory () from
/opt/openoffice.org2.0/program/remotebridge.uno.so
#5 0xb27d2f29 in component_canUnload () from
/opt/openoffice.org2.0/program/liburp_uno.so
#6 0xb27d09a4 in component_canUnload () from
/opt/openoffice.org2.0/program/liburp_uno.so
#7 0xb27c68d5 in component_canUnload () from
/opt/openoffice.org2.0/program/liburp_uno.so
#8 0xb73f02f7 in osl_yieldThread () from
/opt/openoffice.org2.0/program/libuno_sal.so.3
#9 0x00d65b80 in start_thread () from /lib/libpthread.so.0
#10 0x00bd69ce in clone () from /lib/libc.so.6
Andrew
Joerg Budischewski wrote:
in general, OOo indeed crashes when you get an unexpected connection
closure, please check, if you get a core.
If OOo does not crash, it may also be possible, that the office
terminates faster than it can put the reply for terminate on the wire.
AFAIK the office does not wait for remote connections to be dropped
before it terminates.
If the latter is the case, this is difficult to fix. I'd try to ignore
the disposed exception on terminate. Another (more complicated)
workaround can be, that you implement a component inside the office,
which does the terminate call on the desktop delayed (by creating an
own thread that waits form some milliseconds), but that sounds
overkill to me.
Bye,
Jörg
Andrew Z wrote:
Hello,
I am having strange problems with PyUNO and OOo 2.0.1rc1 on Linux.
In some situations, I get the following error on desktop terminate():
uno.com.sun.star.lang.DisposedException: URP_Bridge : disposed\n(tid=3)
Unexpected connection closure
Observations:
- The unexpected closure happens reliably with Xvfb and on a warm start.
- The closure does not happen with Xvfb on a cold start (first attempt).
- The closure does not happen with Xvfb on a warm start if Python
sleeps 2 seconds before terminate().
- The closure does not happen with a real X server.
- Some documents do not cause the error (but observations above refer to
a blank Word document).
My simplified program simply opens OOo, opens a document, closes
document, and closes OOo. The program, scripts for running it
through Xvfb, and a
sample document are here:
http://narnia.dnsalias.org/ooo/uno-disconnect.zip (3.9KB)
The purpose of the full version of my program is automating testing
of OpenOffice.org itself, and unfortunately, the unexpected closure
is the same error PyUNO gives when OpenOffice.org crashes.
Is this unexpected closure problem the fault of OOo, PyUNO, or my
program? How can it be fixed?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
