Issue 17725 - "pthread_mutex_destroy: mutex is still in use" when initializing templates for first time use
Summary: "pthread_mutex_destroy: mutex is still in use" when initializing templates fo...
Status: CLOSED DUPLICATE of issue 14255
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: dankegel
QA Contact: issues@sw
URL:
Keywords: crash, oooqa
Depends on:
Blocks:
 
Reported: 2003-07-31 17:05 UTC by dankegel
Modified: 2013-08-07 14:43 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description dankegel 2003-07-31 17:05:56 UTC 
I ran into this while reproducing issue 8492.  Kai requested I open
a new issue for just the valgrind error.

0. Find a Red Hat 8.0 x86 system (others may do, but that's what I used)
1. Install valgrind 1.9.6.
2. Delete the ~/OpenOffice1.1 directory.
3. Do a net install into your ~/OpenOffice1.1 directory
4. Run OpenOffice under Valgrind (see
http://kegel.com/openoffice/#valgrind)
5. Create a template.  The dialog box "Initializing templates for
first time use" should pop up, and the stack traceback of the problem
should appear in the valgrind log.

Here's the first bit of the log:
pthread_mutex_destroy: mutex is still in use
   at 0x41384C9D: pthread_error (vg_libpthread.c:292)
   by 0x41385B49: __pthread_mutex_destroy (vg_libpthread.c:1002)
   by 0x40979D4F: osl_destroyMutex (in
/opt/OpenOffice.org1.1beta2/program/libsal.so.3.1.0)
   by 0x44F991EB: (within /opt/OpenOffice.org1.1beta2/program/libucb1.so)
   by 0x44F7DD06: (within /opt/OpenOffice.org1.1beta2/program/libucb1.so)
   by 0x408FF887: cppu::OWeakObject::release() (in
/opt/OpenOffice.org1.1beta2/program/libcppuhelpergcc3.so.3.1.0)
   by 0x44F7DDB9: (within /opt/OpenOffice.org1.1beta2/program/libucb1.so)
   by 0x4A700FC9: (within /opt/OpenOffice.org1.1beta2/program/libucphier1.so)
   by 0x4A6F9A82: (within /opt/OpenOffice.org1.1beta2/program/libucphier1.so)
   by 0x408555B9: ucb::Content_Impl::executeCommand(com::sun::star::ucb::Command
const&) (in /opt/OpenOffice.org1.1beta2/program/libucbhelper2gcc3.so)

Full log at http://kegel.com/openoffice/crash-8492.txt
Comment 1 dankegel 2003-07-31 17:10:58 UTC 
Adding keyword "crash" because this is the kind of bug
that is likely to cause a crash on some systems.
Assigning to Kai as requested
adding cc: sewardj.

I set target to 1.1.1 though I'd much prefer to see this fixed in 1.1,
as I have a feeling the OpenOffice folks do not yet take
this kind of error seriously enough to try to fix
it in the weeks remaining before 1.1.
Comment 2 kai.sommerfeld 2003-08-01 07:51:57 UTC 
Bug: PersistentPropertySet::setPropertyValue()
(ucb/source/core/usbstore.cxx) is buggy - there's a missing
m_pImpl->m_aMutex.release() and additionally, in case of an unexpected
exception, the mutex will also not be released. 

Solution: Rewrite PersistentPropertySet::setPropertyValue() and
PersistentPropertySet::setPropertyValues() (to fix the unexpected
exception problem, which also exists in that function) to use
osl::ClearableGuard instead of manual osl::Mutex::acquire() and
osl::Mutex::release().
Comment 3 kai.sommerfeld 2003-08-01 08:07:21 UTC 
Changing prio, because P2 is only for real and not for potential crashes.
Comment 4 kai.sommerfeld 2003-08-27 15:26:47 UTC 
duplicate of 14255, see my additional notes there.


*** This issue has been marked as a duplicate of 14255 ***
Comment 5 kai.sommerfeld 2003-08-27 15:33:00 UTC 
Dan, for your info, fix for 14255 made it into OO 1.1 RC3.
Comment 6 dankegel 2003-09-21 16:08:54 UTC 
So *that's* how bugs get into "NEW, DUPLICATE" state!
Comment 7 Martin Hollmichel 2004-10-15 15:09:36 UTC 
close issue.