<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:iplaw67@tuta.io" title="Alex Thurgood <iplaw67@tuta.io>"> <span class="fn">Alex Thurgood</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Crash in: SfxBindings::GetSlotPos(unsigned short,unsigned short) Editing."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=108802">bug 108802</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>UNCONFIRMED
</td>
<td>NEEDINFO
</td>
</tr>
<tr>
<td style="text-align:right;">Ever confirmed</td>
<td>
</td>
<td>1
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Crash in: SfxBindings::GetSlotPos(unsigned short,unsigned short) Editing."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=108802#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Crash in: SfxBindings::GetSlotPos(unsigned short,unsigned short) Editing."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=108802">bug 108802</a>
from <span class="vcard"><a class="email" href="mailto:iplaw67@tuta.io" title="Alex Thurgood <iplaw67@tuta.io>"> <span class="fn">Alex Thurgood</span></a>
</span></b>
<pre>@John : thanks for the trace.
No repro on macOS 10.12.5 with
Version: 5.3.4.2
Build ID: f82d347ccc0be322489bf7da61d7e4ad13fe2ff3
Threads CPU : 4; Version de l'OS :Mac OS X 10.12.5; UI Render : par défaut;
Moteur de mise en page : nouveau;
Locale : fr-FR (fr_FR.UTF-8); Calc: group
Seems to be Win only.
@John : my (admittedly limited) understanding of your trace indicates a memory
corruption where two threads (from different apps I assume one of which is LO)
are trying to write to an overlapping memory space allocation.
Could it be that you have changed/upgraded your RAM recently, or perhaps one of
the RAM chips has developed a fault ?
If we can at least eliminate that possibility that would rule out hardware
issues.</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>