<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Crash in: mergedlo.dll"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=132047">132047</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Crash in: mergedlo.dll
</td>
</tr>
<tr>
<th>Product</th>
<td>LibreOffice
</td>
</tr>
<tr>
<th>Version</th>
<td>6.3.5.2 release
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>Windows (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>UNCONFIRMED
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Base
</td>
</tr>
<tr>
<th>Assignee</th>
<td>libreoffice-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>lo@ptoye.com
</td>
</tr></table>
<p>
<div>
<pre>This bug was filed from the crash reporting server and is
<a href="https://crashreport.libreoffice.org/stats/crash_details/e064bb1a-b4a4-411b-ab50-4981444c3a83">br-e064bb1a-b4a4-411b-ab50-4981444c3a83</a>.
=========================================
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>