Bug 114401 - Crash in: dbaccess::ModifyLock::~ModifyLock()
Summary: Crash in: dbaccess::ModifyLock::~ModifyLock()
Status: RESOLVED DUPLICATE of bug 103515
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
5.3.7.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-11 00:57 UTC by jimisen
Modified: 2017-12-14 07:13 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["dbaccess::ModifyLock::~ModifyLock()"]


Attachments
Financial records database in development at time of crash (43.33 KB, application/vnd.sun.xml.base)
2017-12-12 17:35 UTC, jimisen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jimisen 2017-12-11 00:57:13 UTC
This bug was filed from the crash reporting server and is br-6d205f3f-3364-4d42-90d9-66a4265bfeb9.
=========================================
Created form, edited List field, saved form, closed Base. Crashed.
Comment 1 Xisco Faulí 2017-12-11 09:15:17 UTC Comment hidden (obsolete)
Comment 2 jimisen 2017-12-12 17:35:35 UTC
Created attachment 138401 [details]
Financial records database in development at time of crash
Comment 3 Alex Thurgood 2017-12-13 10:40:55 UTC
The automatic backtrace provided by the OP indicates that the option "Autorecovery/Auto-backup" has been set. The crash appears to occur because the normal thread is waiting for a mutex lock to be managed correctly from the autorecover function that never happens, and which leads to corruption of the data structure in the ODB.


Setting the autorecovery option was known, for example, to crash LO (see bug 103667 and bug 103515). This was alleged to be fixed in master, but I don't know whether it was backported to 5.3.x (probably not).


@jimisen : you probably need to upgrade to the latest 5.4.x of LibreOffice to make this problem go away.

*** This bug has been marked as a duplicate of bug 103667 ***
Comment 4 Xisco Faulí 2017-12-14 07:13:05 UTC

*** This bug has been marked as a duplicate of bug 103515 ***