<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Rainer,<div class=""><br class=""></div><div class="">Sorry this took me so long to follow up on...<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 14, 2022, at 12:21 AM, Rainer Mohr <<a href="mailto:mail@divelogs.de" class="">mail@divelogs.de</a>> wrote:</div><div class=""><div class=""><blockquote type="cite" cite="mid:C8B72806-E975-4A7F-9C80-3D84659489BF@hohndel.org" class=""><div class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">
Realized, that there are a few dives missing, so I get
them from <a href="http://divelogs.de/" class="" moz-do-not-send="true">divelogs.de</a>. Download works
fine, but after clicking "apply" it tries to merge an then
crashes. Can reproduce any time. Report attached<br class="">
<br class="">
This "apply" and merge <b class="">does</b> work on a
local logbook. <br class="">
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
So this means that it's some odd random memory corruption that
happens in one scenario, not in another, because otherwise it
should crash in both scenarios.</div>
</blockquote>
<br class="">
strange, yes, if i open my cloud logbook, save it locally and then
do the import it crashes too.<br class=""></div></div></blockquote><div><br class=""></div><div>So I tried this three different ways:</div><div><br class=""></div><div>(1) opened from the cloud storage</div><div>(2) opened from a local cloned repo</div><div>(3) opened from a local .ssrf file</div><div><br class=""></div><div>Then I import from the <a href="http://divelogs.de" class="">divelogs.de</a> repo that you made available for me (thanks for that).</div><div><br class=""></div><div>In all three cases I get no crash, in all three cases memory consumption spikes to close to 4G (wow), in all three cases I get a corrupt cylinder index, and since that one changes depending on which way I open things, I'm guessing we are reading uninitialized memory "somewhere".</div><div>I tested this on Linux because usually debugging things there is so much easier...</div><div><br class=""></div><div>With all the variability on the Mac side, can you tell me what type of Mac you see the crash on (x86 or m1) and what macOS version you are running? I can try this on a Mac as well, and of course I'll run this under a memory debugger here to see if that shows any obvious bugs...</div><div><br class=""></div><div>/D</div><div><br class=""></div></div></div></body></html>