Bug 132047 - Crash in: mergedlo.dll
Summary: Crash in: mergedlo.dll
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.3.5.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-11 09:31 UTC by Peter Toye
Modified: 2020-10-17 18:47 UTC (History)
3 users (show)

See Also:
Crash report or crash signature: ["mergedlo.dll"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Toye 2020-04-11 09:31:34 UTC
This bug was filed from the crash reporting server and is br-e064bb1a-b4a4-411b-ab50-4981444c3a83.
=========================================
As far as I can remember what happened was:

1) I ran a macro which saves the current database under a new name (some time ago I had corruption problems)

2) Got a message saying the LibO had crashed. This must have happened fairly on in the macro as it produces a Msgbox which didn't happen.

3) Produced this bug report.

Then there were many further problems: on restarting LibO it did a recovery and then went into a startup loop - showing the splash screen which disappeared and reappeared. Managed to kill the LibO tasks. Tried starting it up again and it offered a crash report (declined) and then suggested I should start in safe mode. Did that, and went back to a 'last known working' profile. Got the document back again and it seems to be OK.

There seem to be stability problems. I'd not used the backup macro since July 2019, so can't help to work out where the bug appeared. 

I have just run the macro from a test version and that seems to be OK, so I am worried about either a database corruption in the running version (but the queries & reports seem to be OK)

I'd be happy to send a copy of the offending database (about 200kb) to see if anyone else can reproduce the problem.
Comment 1 Xisco Faulí 2020-04-17 11:02:37 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 2 QA Administrators 2020-10-15 04:11:25 UTC Comment hidden (obsolete)
Comment 3 Peter Toye 2020-10-17 16:13:43 UTC
Very sorry about this - I had serious health problems and it slipped my mind.

I've tried it again in version 6.4.2 and it seemed to work, so I'll mark it as Resolved and hope it doesn't happen again.