[TC8.0RC1 x64] Crash with read-only wincmd.ini

umbra · Post by *umbra » 2012-05-10, 19:19 UTC

For test purposes I have a portable TC with read-only fresh wincmd.ini, so every time I start a new instance it automatically starts with clean ini. And that's how I found this bug.

1. Extract/install/whatever TC, so you have a fresh installation
2. Make sure, its wincmd.ini is not writable and there is no wincmd.key either
3. Start TC, you should see the nag-screen
4. Close the nag-screen by pressing the appropriate number on keyboard, not by mouse
5. Close the options dialog

The dialog looses its modality but stays visible. When you try to close it again, TC crashes.
Only 64b version seem to be affected (tested 8.0 rc1).

Dalai · Post by *Dalai » 2012-05-10, 22:15 UTC

I can confirm the bug, but TC doesn't crash on my system. Don't know if it matters but I used a wincmd.ini of 0 bytes in size (read-only of course).

Regards
Dalai

umbra · Post by *umbra » 2012-05-10, 22:26 UTC

... I used a wincmd.ini of 0 bytes in size ...

In that case TC should ignore that file and use your system-wide wincmd.ini. As I said, I have that TC in a portable mode ("UseIniInProgramDir=7") isolated from other instances, so that might be a reason why it crashes in my case.

Dalai · Post by *Dalai » 2012-05-10, 22:34 UTC

umbra wrote:
... I used a wincmd.ini of 0 bytes in size ...
In that case TC should ignore that file and use your system-wide wincmd.ini.

That file is the system-wide wincmd.ini. I renamed wincmd.ini and created a new wincmd.ini using Shift+F4.

As I said, I have that TC in a portable mode ("UseIniInProgramDir=7") isolated from other instances, so that might be a reason why it crashes in my case.

OK, I missed that part. Now I set this option in the mentioned wincmd.ini but still no crash. Maybe it "needs" some other setting to crash.

Regards
Dalai

umbra · Post by *umbra » 2012-05-10, 22:40 UTC

You are right. I just retested it. How do you close the options dialog after it looses its modality? It seems that you have to press ENTER again to make it crash. So when you start TC, press number-ENTER-ENTER. Does it crash then?

Dalai · Post by *Dalai » 2012-05-10, 23:18 UTC

umbra wrote:How do you close the options dialog after it looses its modality?

I used the mouse though I know that's not how TC is meant to be used

.

So when you start TC, press number-ENTER-ENTER. Does it crash then?

It closes itself but without a Windows error message, so I wouldn't consider this a crash. I agree that it isn't normal behaviour and shouldn't happen.

Regards
Dalai

umbra · Post by *umbra » 2012-05-10, 23:44 UTC

It closes itself but without a Windows error message, so I wouldn't consider this a crash.

If you are using WinXP, then it's the worst crash an user-level application can experience - it crashed so badly, Windows wasn't even able to show an error. In Vista, they changed the way of handling of these crashes, so I guess, that's why I can see the error.

But anyway, thanks for confirming it.

Post by *ghisler(Author) » 2012-05-11, 10:20 UTC

Actually what happens is that the configuration dialog is opened _twice_. This should be fixed in RC2 now.

umbra · Post by *umbra » 2012-05-11, 10:27 UTC

Actually what happens is that the configuration dialog is opened _twice_.

Sorry, I didn't notice that. But anyway, RC2 works fine.