Bug 66087 - Other: LibreOffice crashes after choosing Writer with (erroneously) installed Duden Korrektor
Summary: Other: LibreOffice crashes after choosing Writer with (erroneously) installed...
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.0.1 rc
Hardware: Other macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
: 75196 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-06-23 15:22 UTC by bugzilla
Modified: 2014-02-19 15:51 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugzilla 2013-06-23 15:22:32 UTC
As described in bug id 66082, Duden Korrektor was tried to installed in LibreOffice 4.1. The installation aborted but the extension is still in the extension manager (grayed out due to an error). If I try to open the writer from the start center, LibreOffice crashes on Mac OS X. This does not happen with the other applications. N.B.: The Duden Korrektor tool bar is shown in all applications.

Following report is displayed after the crash (extract):
Thread 6 Crashed:
0   libsystem_kernel.dylib        	0x93fc3a6a __pthread_kill + 10
1   libsystem_c.dylib             	0x969c0b2f pthread_kill + 101
2   libsystem_c.dylib             	0x969f74ec abort + 168
3   libuno_sal.dylib.3            	0x0000f55b rtl_compareMemory + 11
4   dudenkorrektor.uno.dylib      	0x103f4d01 Duden::DudenDictionary::getSomething(com::sun::star::uno::Sequence<signed char> const&) + 59
5   dudenkorrektor.uno.dylib      	0x103e4e00 Duden::LoadActiveUserDictionaries(Duden::SessionData&, com::sun::star::uno::Reference<com::sun::star::lang::XMultiServiceFactory> const&, com::sun::star::uno::Reference<com::sun::star::linguistic2::XDictionaryList> const&) + 555
6   dudenkorrektor.uno.dylib      	0x1040d44a Duden::DudenWrapperData::GetOrCreateSessionData(short, short, bool) + 1332
7   dudenkorrektor.uno.dylib      	0x10411756 Duden::DudenWrapper::GetGrammarErrorsForSentence(std::vector<Duden::DpfOffsetsCopy, std::allocator<Duden::DpfOffsetsCopy> >*&, rtl::OUString const&, rtl::OString const&, short, long, long, Duden::ExtraOptions const&) + 70
8   dudenkorrektor.uno.dylib      	0x103ff9e1 Duden::DGrammarChecker::doProofreading(rtl::OUString const&, rtl::OUString const&, com::sun::star::lang::Locale const&, long, long, com::sun::star::uno::Sequence<com::sun::star::beans::PropertyValue> const&) + 933
9   liblnglo.dylib                	0x0fde76cc GrammarCheckingIterator::DequeueAndCheck() + 2092
10  libuno_sal.dylib.3            	0x0000e58e osl_thread_start_Impl + 398
11  libsystem_c.dylib             	0x969bf5b7 _pthread_start + 344
12  libsystem_c.dylib             	0x969a9d4e thread_start + 34              
Operating System: Mac OS X
Version: 4.1.0.1 rc
Last worked in: 4.0.4.2 release
Comment 1 bugzilla 2013-06-23 15:31:08 UTC
After removing the Duden Extension, Writer is working well again. Maybe this is a Extension bug, but I think a crash of the whole application is not wanted.
Comment 2 retired 2013-06-24 06:46:44 UTC
With all those reports of crashes with the Duden plugin and LO 4.x and Duden saying they will no longer develop this plugin, I wonder how we can prevent users from installing this?

Is there an option to disable installation of certain plugins in LO?
Comment 3 Stephan Bergmann 2013-07-11 14:04:11 UTC
Duden Korrektor being closed source, it is hard to tell whether this is a bug in Duden Korrektor or a problem resulting from the extension being only half-installed due to the unexpected "javaloader error - no mapping from java to C++" failure during installation discussed in bug 66082.  (If the latter, see <http://cgit.freedesktop.org/libreoffice/core/commit/?id=57955e1961181ffe7e77c23da7fb73db5d545f4c> "Revert 'Cleanly remove an extension again that cannot be activated while installing it'" for problems getting that fixed.)
Comment 4 Stephan Bergmann 2014-02-19 15:51:44 UTC
*** Bug 75196 has been marked as a duplicate of this bug. ***