Re: Crash on Mac OSX

On 09/09/2013 12:31 PM, Ovidiu-Florin Bogdan wrote:
> A coworker of mine is working on a LibreOffice extension and LO crashes
> with the following errors on Mac OSX 10.6.8:
>
> 1. This hapens after the extension is uninstalled from the LO gui and LO
> is closed: http://paste.kde.org/p00afad8c/37830010/ (pass: LO123 )

Is this reproducible, or did it happen just once?

> Thread 4 Crashed:\
> 0   libupdchk.dylib                     0x17c4092e UpdateHandler::loadStrings() + 62\
> 1   libupdchk.dylib                     0x17c42039 UpdateHandler::getBubbleTitle(UpdateState) + 57\
> 2   libupdchk.dylib                     0x17c259f2 
> UpdateCheck::handleMenuBarUI(rtl::Reference<UpdateHandler>, UpdateState&, bool) + 130\
> 3   libupdchk.dylib                     0x17c28389 UpdateCheck::setUIState(UpdateState, bool) + 473\
> 4   libupdchk.dylib                     0x17c29ab5 
> UpdateCheck::initialize(com::sun::star::uno::Sequence<com::sun::star::beans::NamedValue> const&, 
> com::sun::star::uno::Reference<com::sun::star::uno::XComponentContext> const&) + 1333\
> 5   libupdchk.dylib                     0x17c3950f (anonymous 
> namespace)::InitUpdateCheckJobThread::run() + 79\
> 6   libupdchk.dylib                     0x17c2bc22 threadFunc + 18\
> 7   libuno_sal.dylib.3                  0x0000e58e osl_thread_start_Impl + 398\
> 8   libSystem.B.dylib                   0x94bb0259 _pthread_start + 345\
> 9   libSystem.B.dylib                   0x94bb00de thread_start + 34\

means that the thread that checks for LO updates happens to be running 
at an "inappropriate" time (presumably while "LO is closed," as you 
state).  That thread is started a little while after LO starts up, and 
it is a well-known problem (though still without a fix) that that thread 
can lead to crashes if it is still active during shutdown.

> 2. This hapens when we try to install the extension from command line:
>
> {\rtf1\ansi\ansicpg1252\cocoartf1038\cocoasubrtf360
>
> {\fonttbl\f0\fnil\fcharset0 Monaco;}
>
> {\colortbl;\red255\green255\blue255;}
>
> \margl1440\margr1440\vieww14600\viewh14260\viewkind0
>
> \deftab720
>
> \pard\pardeftab720
>
> \f0\fs22 \cf0 [2013-09-04 13:10:49, 782ms]\
>
> INFO: CVS.ExtensionsManager.Platform.IOperatingSystem run\
>
> Start executing command:
> /Applications/LibreOffice.app/Contents/MacOS/\ul unopkg\ulnone add -f -v
> \ul addins\ulnone /Calc_Adaptor_0.0.2/OOQEL_002.\ul oxt\ulnone \
>
> \
>
> [2013-09-04 13:11:05, 665ms]\
>
> INFO: CVS.ExtensionsManager.Platform.IOperatingSystem run\
>
> Stream type: ERROR\
>
> \
>
> ERROR: Binary URP bridge disposed during call\
>
> Exception details: \
>
> (com.sun.star.lang.DisposedException) \{ \{ \{ Message = "Binary URP
> bridge disposed during call", Context = (com.sun.star.uno.XInterface)
> @4b25c70 \} \} \}\
>
> \
>
> \pard\pardeftab720
>
> \cf0 \ul \ulc0 unopkg\ulnone failed.\

Hard to tell whats going wrong without access to the extension's source 
code.  In general, unopkg will connect to either an soffice process if 
one is already running, or spawn a uno.bin process and connect against 
that, and communicate via LO's UNO remote protocol (URP), and "Binary 
URP bridge disposed during call" typically means that that other process 
(i.e., soffice or uno.bin) crashed.

Stephan

PS, please generate (preferably plain text) mails that are readable, 
without what looks like RTF noise.