Bug 62782

Josep, could you also attach the document that produces the crash?

Does the crash happen with every document you use writer with or only one specific.

I'm on 10.8.3 and use LO 4.0.1.2 without any hiccups so far.

I can't attach the document. On the other hand, I can't confirm that the problem is related with this document for I'm working simultanously with difeferent docuemnts -in other windows and so on- during hours. And when the program crashes there is already no document active. In fact, when I open a text and work only a few, normaly I have no problem. 

Thanks for your answer and attention.

(as the crash was in AquaClipboard::applicationDidBecomeActive, it is more likely that it was related to preceding copy/paste operations than to a specific document that was open)

Josep: do you reproduce this after having renamed your LO directory profile? (see https://wiki.documentfoundation.org/UserProfile)

Also:
- did you install any specific fonts?
- did you install LO extensions?
- what's the language of your UI and of your file?

And as I do sometimes with MacOs related bugs, I quote Roman's questionnaire:
"
Here is my complete standard “questionnaire” for such issues:
-------------------------------------------------------------------------------

1) Do you have any accesibility features enabled? Apple’s accessibility
features like “VoiceOver” or “Enable access for assistive devices”, which get
enabled in “System Preferences > Universal Access”, are known to cause many crashes and freezes in LibreOffice. So please try to disable any accesibility features, then check if the problem is still reproducible.

2) Do you have installed any window management/user interface utilities/apps/control panels/extensions for Mac OS X like 
   * AquaSnap                * BetterSnapTool
   * BetterTouchTool         * Breeze
   * Cinch                   * Divvy
   * DoublePane              * Flexiglass
   * HyperDock               * iSnap
   * Moom                    * RightZoom
   * ShiftIt                 * SizeUp
   * SizeWell                * Spectacle
   * Stay                    * TileWindows
   * WindowTidy            ... or something similar?

And/or do you use any mouse cursor/pointer utility, i.e. some little application or control panel etc. which animates or replaces etc. the mouse curser/pointer, like
   * LazyMouse?

And/or do you use any special software which could be related to accessibility stuff, e.g. a screen reader, screen magnifier, speech recognition software,
a text-to-speech (dictation) application, or similar?

All these and many similar utilities rely heavily on Mac OS accessibility features and therefore can cause LibreOffice to crash or freeze. So please check if you have installed any utility of this kind and try to disable it
(or to add LibreOffice to the list of excluded applications for the utility,
if there is such a thing).
"

I don't understand why would I have to rename my user profile.

About the rest of questions:

-I have installed Gentium fonts.
-I have some extensions (connector to zotero, for exemple). But I don't remember all the extensions...
-The UI language is catalan and the language of the document catalan (and spanish for some paragraphs). 
-I didn't enable accesibility features.
-I didn't installed any window management/user interface utilities/apps/control panels/extensions for Mac OS X.
-But I use a Bamboo Tablet in order to process pictures and moreover as a mouse. In this sense I'll open perhaps another bug-report in the future, since I think this Bamboo Tablet perhaps causes some problems with the vertical movement bar, in the right of the LO window.  

Thanks for your attention,

Josep

Josep:

Thank you for your feedback. For the test, could you unplug Bamboo tablet?

About renaming your LO directory profile, it would allow LO to recreate a brand new one so it could launch without :
- any leftovers of a previous version
- any extensions installed
- any customization

@Stephan:
Do we already have enough info or should we close this one because of reporter's inactivity?

I didn't report anything more for two reasons:

1) For a certain time I didn't have any problem more. But I don't know why. In fact, I didn't change anything. I was surprised ...and aiting.

2) After this time I have upgraded to the next version, the 4.0.2.2 version, which works fine, referred to this issue.

Thanks for your attention.

(In reply to comment #8)
> I didn't report anything more for two reasons:
> 
> 1) For a certain time I didn't have any problem more. But I don't know why.
> In fact, I didn't change anything. I was surprised ...and aiting.
> 
> 2) After this time I have upgraded to the next version, the 4.0.2.2 version,
> which works fine, referred to this issue.
> 
> Thanks for your attention.

In the third line: "and waiting",not "*aiting".

The backtrace in attachment 77082 [details] looks odd, in that SfxApplication::GetOrCreate should go into SfxApplication::Initialize_Impl only the first time it is called, which would be from within desktop::Desktop::Main calling com::sun::stsar::frame::GlobalEventBroadcaster::create, way before desktop::Desktop::Main calls Application::Execute.

So if this backtrace is indeed from an soffice instance that crashed after you did some work with it (rather than from an soffice instance that crashed instantly upon startup), the most likely explanation is that it is fallout from some other bug corrupting memory.

As this is reportedly not (any longer) reproducible, we cannot do much about it, so I'm closing for now.  Feel free to re-open if it happens again.

Normaly, first I close the app and after I quit it. At this moment it used to crash.

Thanks for your answer. If the problem appears again, I'll reopen the issue.