Windows crash

[Dirk Hohndel]

> On Mar 30, 2021, at 12:26 AM, Berthold Stoeger <bstoeger at mail.tuwien.ac.at> wrote:
> 
> On Dienstag, 30. März 2021 05:32:37 CEST Dirk Hohndel via subsurface wrote:
>> The consistent trigger appears to be closing a dive file. My guess is that
>> some destructor gets called twice or that in some other way we access freed
>> memory.
>> 
>> I tried to figure this out by starting at valgrind output on Linux, but so
>> far I haven't managed to figure it out...
> 
> It seems that on reset, the statistics code gets a selection-changed signal 
> before getting a data-reset signal. This means that the statistics code is 
> accessing stale dive data. The joy of control-flow by callbacks (signals).

So just add a global variable that... never mind :-)

I wonder why I didn't find this with Valgrind. Given that my professional software 
developer career started writing a memory debugger 27 years ago... I find Valgrind
frustratingly inconsistent to use.

/D