Beta 6 crash on exit, sometimes

[Jibz]

With the latest beta 6 of TC7.5 I've noticed it sometimes crashes on exit. It isn't all the time and I haven't been able to reproduce any steps leading to it, but it seems to happen after I've used it for a while only. I press the X in the upper right corner to close TC and get this dialog:

Image: http://i41.tinypic.com/t6qexi.jpg

I am not using any plugins, and I never had this happen with any of the previous betas, but it happens a couple of times a day with beta 6.

[MVV]

I test beta 6 at home and at work, but never seen such bug.

[HolgerK]

I am not using any plugins, and I never had this happen with any of the previous betas, but it happens a couple of times a day with beta 6.

Any chance that you installed another application at the same time which installed a faulty shell extension (Context menu, Icon handler, ...)?
These will unload at exit too, and sometimes causing troubles because terminating seems to be an unexpected behavior (Explorer.exe normally never close, except at shutdown).

Regards
Holger

[Jibz]

The only other updates coinciding were Beyond Compare and FileZilla .. it is of course possible that they introduced a bug in the latest versions, but wouldn't that give a similar behavior in other programs as well then?.

[ghisler(Author)]

How exactly do you close Total Commander? Mouse? Keyboard? How exactly? There is no stack trace, which is indicating that the error is happening outside of the code controlled by Total Commander. Or did you use one of the standalone tools (lister, sync, compare by content)?

[Jibz]

I press the X in the upper right corner to close TC

I was thinking the same about the error dialog. Usually it should have contained some stack trace information shouldn't it. I will let you know if I figure out any problem with FileZilla or Beyond Compare.

[Clo]

2ghisler(Author)

Good evening,

Jibz wrote

…I press the X in the upper right corner to close TC…

• I ought say that I do so at least 20 times a day and didn't get any crash…
… and that here, neither FileZilla nor Beyond Compare is installed !

 VG
Claude
Clo

[Jibz]

It seems to have disappeared since I updated FileZilla again, so I am hoping that was what caused it.

Thanks to HolgerK for the useful post.

[ghisler(Author)]

I got the error once too, so I will try to find a solution.

[ghisler(Author)]

Can you still reproduce that error with beta 7? If yes, can you post the error message, please?

[Marco Artale]

I have the problem with beta7.

The same behaviour and when I close with X button.

It seems that is more frequent when I open "Netbeans ide 6.7"

That makes me think that is something related with java runtime.

[Balderstrom]

Is it possible NetBeans or another application has a memory leak and is writing into TC's memory space? I've seen some oddities with Xnews - similiar to this, though it didn't relate to Total Commander. It used to happen far more often under Win98 than Win2K.

I've had a couple crashes with TC 7.5b6, but I couldn't reproduce them - seemed to happen when messing around frequently with the IconBar.

[ghisler(Author)]

Please post the error message from beta 7! Maybe it gives me a clue of what is happening...

[HAL 9000]

PB7 - Always crashes on exit. Error code is either as the first post (image by Jibz) (most often) or code 0xdeadfade.

Significant things about that computer are:

- it's a Windows Server 2003,
- the crash always appears after browsing through local network (workgroup),
- if I don't browse through network it might not happen,
- the only shell extension is WinRar.
- Processor is old Athlon XP,
- the crash never happens if ProcMon is active!

*Edit: the following is not very accurate:

- It didn't crash on exit until (around) PB5
- PB5 crashed all the same
- PB6 crashed less often or never (didn't use it very long)
- In other PB-s of older releases the same crash also happenned in the first few betas, but was usually resolved by final releases

[ghisler(Author)]

Well, at least the error code is funny, it contains the words "dead" and "fade".

Did you try to turn off the background thread for reading dirs as described in another thread?

wincmd.ini
[Configuration]
ThreadFindFirst=0