Bug 577525

Summary: [abrt] crash in ImplRegionBase::~ImplRegionBase (SIGABRT) (threading?)
Product: [Fedora] Fedora Reporter: mdmpsyd <mdmpsyd>
Component: openoffice.orgAssignee: David Tardon <dtardon>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: caolanm, dilworthscott, dtardon, johnmargaritopoulos
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:8fcdb6ac5ed7e4d82ca52d0b7a93776db0c0f626
Fixed In Version: openoffice.org-3.3.0-18.2.fc14 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-28 20:59:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description mdmpsyd@gmail.com 2010-03-27 19:10:13 UTC
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer
component: openoffice.org
executable: /usr/lib/openoffice.org3/program/swriter.bin
kernel: 2.6.32.9-70.fc12.i686.PAE
package: openoffice.org-writer-1:3.1.1-19.28.fc12
rating: 4
reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 mdmpsyd@gmail.com 2010-03-27 19:10:15 UTC
Created attachment 403027 [details]
File: backtrace

Comment 2 David Tardon 2010-03-27 19:50:01 UTC
I feel this is a threading problem: an Invalidate() call without acquiring the SolarMutex, which incidentally clashed with repaint running from the main thread. It seems there are at least four methods of ExtensionBox_Impl calling Invalidate() and only one (checkEntries) is called with the SolarMutex acquired. But I'd be very glad to get Caolan's opinion on this.

dtardon->mark: Can you reproduce the crash? If it really is a threading issue, I wouldn't expect 100 % reproducibility, but at least sometimes?

Comment 3 mdmpsyd@gmail.com 2010-03-28 02:03:26 UTC
(In reply to comment #2)
> I feel this is a threading problem: an Invalidate() call without acquiring the
> SolarMutex, which incidentally clashed with repaint running from the main
> thread. It seems there are at least four methods of ExtensionBox_Impl calling
> Invalidate() and only one (checkEntries) is called with the SolarMutex
> acquired. But I'd be very glad to get Caolan's opinion on this.
> 
> dtardon->mark: Can you reproduce the crash? If it really is a threading issue,
> I wouldn't expect 100 % reproducibility, but at least sometimes?    

If I remember correctly (and I'm not positive I do), I had the extension manager open and was looking for and applying updates. I tried to reproduce but the updates had all been installed. Is there an easy way to undo the updates so I can attempt to reproduce?

Comment 4 David Tardon 2010-03-28 05:22:31 UTC
Afraid not :( The only way is to remove the extension and install older version of it.

Comment 5 Caolan McNamara 2010-04-01 12:14:09 UTC
caolanm->dtardon: Sounds plausible anyway that any routes that might end up in Invalidate should take a SolarMutex, e.g. ExtMgrDialog::addPackageToList and friends. Can you take that up with upstream and clarify if that's the case.

Comment 6 David Tardon 2010-06-03 07:40:26 UTC
Well, upstream haven't said a word in over two months and there has been no other report for the same problem so far, so I'm taking the liberty to close this UPSTREAM. I'll reconsider commiting the fix to Fedora if there is another report for the same thing.

Comment 7 Caolan McNamara 2010-06-19 16:18:32 UTC
*** Bug 605931 has been marked as a duplicate of this bug. ***

Comment 8 David Tardon 2010-12-19 15:52:05 UTC
*** Bug 664072 has been marked as a duplicate of this bug. ***

Comment 9 David Tardon 2010-12-19 15:54:21 UTC
We have got another dupe of this and upstream has accepted the patch meanwhile, so I'm going to push it into Fedora after all.

Comment 10 David Tardon 2010-12-20 10:10:05 UTC
fixed in openoffice.org-3.2.0-12.35.fc13 and openoffice.org-3.3.0-18.2.fc14

Comment 11 Fedora Update System 2010-12-21 12:09:25 UTC
openoffice.org-3.3.0-18.2.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/openoffice.org-3.3.0-18.2.fc14

Comment 12 Fedora Update System 2010-12-21 23:57:21 UTC
openoffice.org-3.3.0-18.2.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update openoffice.org'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/openoffice.org-3.3.0-18.2.fc14

Comment 13 Fedora Update System 2010-12-28 20:59:15 UTC
openoffice.org-3.3.0-18.2.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.