To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
                 Issue #|112605
                 Summary|[sw] crash during shutdown: no SolarMutex
               Component|Word processor
                 Version|DEV300m80
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P4
            Subcomponent|code
             Assigned to|mst
             Reported by|mst





------- Additional comments from [email protected] Tue Jun 22 15:03:51 +0000 
2010 -------
just captured this most peculiar critter:

alDisplay::~SalDisplay()
SalDisplay::DeInitRandR()
GtkXLib::~GtkXLib()
==26317== Thread 7:
==26317== Invalid read of size 4
==26317==    at 0xA6B2081: Application::GetSolarMutex() (svapp.cxx:528)
==26317==    by 0x1DE39D19: sw::UnoImplPtr<SwXTextCursor::Impl>::~UnoImplPtr()
(unobaseclass.hxx:126)
==26317==    by 0x1DE34AF1: SwXTextCursor::~SwXTextCursor() (unoobj.cxx:919)
==26317==    by 0x74F7C0D: cppu::OWeakObject::release() (in
inst/OO_m80_pooltest_li/OOo_DEV300m80_Linux_x86_install-arc_en-US/openoffice.org/ure/lib/libuno_cppuhelpergcc3.so.3)
==26317==    by 0x1DE39A38:
cppu::WeakImplHelper12<com::sun::star::lang::XServiceInfo,
com::sun::star::beans::XPropertySet, com::sun::star::beans::XPropertyState,
com::sun::star::beans::XMultiPropertyStates,
com::sun::star::container::XEnumerationAccess,
com::sun::star::container::XContentEnumerationAccess,
com::sun::star::util::XSortable, com::sun::star::document::XDocumentInsertable,
com::sun::star::text::XSentenceCursor, com::sun::star::text::XWordCursor,
com::sun::star::text::XParagraphCursor,
com::sun::star::text::XRedline>::release() (implbase12.hxx:120)
==26317==    by 0x1DE2C714: SwXTextCursor::release() (unoobj.cxx:3199)
==26317==    by 0x101932F7: ??? (in
inst/OO_m80_pooltest_li/OOo_DEV300m80_Linux_x86_install-arc_en-US/openoffice.org/ure/lib/libgcc3_uno.so)
==26317==    by 0x75ABAA9: ??? (in
inst/OO_m80_pooltest_li/OOo_DEV300m80_Linux_x86_install-arc_en-US/openoffice.org/ure/lib/libuno_cppu.so.3)
==26317==    by 0x75B4108: ??? (in
inst/OO_m80_pooltest_li/OOo_DEV300m80_Linux_x86_install-arc_en-US/openoffice.org/ure/lib/libuno_cppu.so.3)
==26317==    by 0x75B4181: uno_Environment_invoke_v (in
inst/OO_m80_pooltest_li/OOo_DEV300m80_Linux_x86_install-arc_en-US/openoffice.org/ure/lib/libuno_cppu.so.3)
==26317==    by 0x75B41B4: uno_Environment_invoke (in
inst/OO_m80_pooltest_li/OOo_DEV300m80_Linux_x86_install-arc_en-US/openoffice.org/ure/lib/libuno_cppu.so.3)
==26317==    by 0x75A73A9: ??? (in
inst/OO_m80_pooltest_li/OOo_DEV300m80_Linux_x86_install-arc_en-US/openoffice.org/ure/lib/libuno_cppu.so.3)
==26317==  Address 0x4 is not stack'd, malloc'd or (recently) free'd
==26317== 
==26317== 
==26317== Process terminating with default action of signal 11 (SIGSEGV)
==26317==  Access not within mapped region at address 0x4
==26317==    at 0xA6B2081: Application::GetSolarMutex() (svapp.cxx:528)
==26317==    by 0x1DE39D19: sw::UnoImplPtr<SwXTextCursor::Impl>::~UnoImplPtr()
(unobaseclass.hxx:126)
==26317==    by 0x1DE34AF1: SwXTextCursor::~SwXTextCursor() (unoobj.cxx:919)


so it seems that during shutdown the SolarMutex may actually be 0... but
Application::GetSolarMutex() returns a reference, not a pointer...
[ but a crash during shutdown won't impact the user much and isn't so 
important... ]

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to