Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Mac: Deadlock while installing extensions | ||||||
---|---|---|---|---|---|---|---|
Product: | General | Reporter: | kai.sommerfeld | ||||
Component: | code | Assignee: | joerg.skottke | ||||
Status: | CLOSED FIXED | QA Contact: | issues@framework <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | hdu, issues, maho.nakata, nesshof, olaf-openoffice, philipp.lohmann, stefan.baltzer, uwe.luebbers | ||||
Version: | OOO300m4 | Keywords: | aqua | ||||
Target Milestone: | OOo 3.0 | ||||||
Hardware: | Mac | ||||||
OS: | Mac OS X, all | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Issue Depends on: | |||||||
Issue Blocks: | 88888, 92214 | ||||||
Attachments: |
|
Description
kai.sommerfeld
2008-09-05 11:58:27 UTC
mh: This is a 3.0 show stopper. @hdu: as discussed. there seem to be two mutexes involved: - the solar mutex - an internal Cocoa mutex The extension installation thread holds the solar mutex and indirectly tries to get the Cocoa mutex when it creates a dialog. The main thread already holds the Cocoa mutex when NSView::drawRect is called and its YIELD_GUARD waits on the solar mutex => a classical dead lock Created attachment 56271 [details]
suggested hotfix
Fixed in CWS i93512 @mh: please decide if this problem block issue 88888 @jsk: please verify in CWS i93512 add to blocker list. SBA->JSK: As discussed, I found a scenario to reproduce: - Start an En_US installation of OOo - Tools-Extension Manager - Click "Add" - Select a dict extension that is already installed (i.e. En_US) - In upcoming dialog, click "For All Users" - [Now the dialog "...already installed, do you wish to replace..." should come up] -> Deadlock. Verified the fix for this scenario in CWS i93512. @pl: undoing your change for issue 92075 in CWS vcl30stop2 http://gsl.openoffice.org/source/browse/gsl/vcl/aqua/source/window/salframe.cxx? r1=1.66&r2=1.66.16.1 seems to fix this deadlock too. Fixed in Master Tested with 3.0.0 RC1 PPC Version on Tiger Closing Issue rbircher: Sorry, but the fix cannot be in the master yet, because the corresponding CWS is not yet integrated. It might be the case that you did not encounter the deadlock on your system. This is the nature of this bug. It does not occue always and everywhere. Reopening. Restoring correct bug status (1) Restoring correct bug status (2) No deadlock in m9, closing |