Hi Alex,
I'm having trouble reproducing this; perhaps it is bugs on our side;
certainly installing the extension on master fails on install; I'm doing
a fresh 3.3.0 build now to test;
I was wondering; if you could run soffice.bin inside gdb - and get a
stacktrace from that (thread apply all backtrace) with debugging symbols
from your crash-on-exit.
We have fixed a number of memory leaks in 3.3, and sadly some code, off
the beaten path, may depend on the leaks still. Also - responses to the
freedesktop bugzilla much appreciated.
Thanks !
Michael.
--
[email protected] <><, Pseudo Engineer, itinerant idiot
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/1294915831.23305.40.camel@lenovo-w500
