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). Berthold _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
