Problems with multiple open DataSeeker windows

[Andreas Schnellbacher]

In the past, I noticed crashes when multiple DataSeeker windows exist. Unfortunately, I couldn't find a scheme when that happens and when not. I'll report relevant observations here.

The bug most likely just occurs after switching between these windows and after executing a search then.

More details have to be added.

[Andreas Schnellbacher]

I remember one more detail: The data of DATASEEK.INI seems to be corrupted after such a crash. After that, DataSeeker opens either with a tiny window size or it was hidden, I don't remember anymore. Additionally, I'm sure that's not a shared memory problem, that cause the writing of corrupt ini data.

Because I use DataSeeker often, I try to avoid multiple windows. That makes reproducing it harder. ;-)

[andib]

I use more than one instances of DataSeeker at the same time very often. But do not see your problem until now.

I care about which window I close as last one cause the settings of this one are that one which end up in the final ini file.

I guess it can make a lot of problems when two instances of DataSeeker try to write different data to the ini file at the same time. I 'think' the ini file is read at program start and written at program end. But maybe there are other circumstances which changes the ini file in between. If yes this may lead to your problem.

One other thought comes to mind - could it be that you use two different versions of DataSeeker? I saw ini file corruptions only when switching versions. I think I build into some version check and if not matching the ini entries will be cleared partly. Cause otherwise there were all sort of crashes.

[Andreas Schnellbacher]

Andi, thanks for your reply. Unfortunately I had forgotten that the Trac notification doesn't work on netlabs.org.

I have checked all types how I could have started dataseek.exe. Unfortunately there remains too little chance that your guess was true for my case.

The positive message: I've tried to reproduce it again and it won't happen again. (I'm sure it did in some earlier version.) Therefore I'll close the ticket. (I created it mostly as a reminder for me and your negative diagnosis helps me to come to the current state.) Thanks again.

[Andreas Schnellbacher]

After some months of usage without a crash, I can confirm that the issue is fixed.

[andib]

Thanks for reporting.