TC75b7 access violation on exit

[ghisler(Author)]

The problem seems to be the thread which is used for FindFirstFile when ThreadFindFirst was on (which is now the default in TC 7.5). I'm working on a solution, but it's very difficult because I do not get any crash here. It seems to be some sort of timing problem. Do you all have multi-core systems (core-duo, core-quad etc.) or does anyone experience this also on a single core system? My development system is single core, but I don't get the error on a dual core system either...

[jy307@columbia.edu]

With respect to multi-core my machine is a relatively old hp so I dont think so. However the device manager says that I have ACPI multiprocessor computer. cpuz says:

-------------------------
CPU-Z version 1.41
-------------------------

Processors Map
------------------------------------------------------------------------------------

Number of processors 1
Number of threads 2

Processor 0
-- Core 0
-- Thread 0
-- Thread 1


Processors Information
------------------------------------------------------------------------------------

Processor 1 (ID = 0)
Number of cores 1
Number of threads 2 (max 2)
Name Intel Pentium 4 530
Codename Prescott
Specification Intel(R) Pentium(R) 4 CPU 3.00GHz
Package Socket 775 LGA (platform ID = 4h)
CPUID F.3.4
Extended CPUID F.3
Core Stepping D0
Technology 90 nm
Core Speed 3000.9 MHz (15.0 x 200.1 MHz)
Rated Bus speed 800.2 MHz
Stock frequency 3000 MHz
Instructions sets MMX, SSE, SSE2, SSE3
L1 Data cache 16 KBytes, 8-way set associative, 64-byte line size
Trace cache 12 Kuops, 8-way set associative
L2 cache 1024 KBytes, 8-way set associative, 64-byte line size
FID/VID Control no
Features

[jvh]

I have both PC's with single core CPU (AMD Athlon 64 3700+ and AMD Athlon 64 3700+).

And there is UUE encoded part of my wincmd.ini with non-default values:

Code: Select all

begin 644 wincmd.zip
M4$L#!!0``@`(`&R<]SKH/L*3\0(``*0%```*````=VEN8VUD+FEN:954P6[;
M,`R]!\A?+)<=BB9;NVZ`#XZ=+,&<Q(O3M5A3%(K-Q$)ER9#DMM[7CY3MIFNW
MPVXR)9*/C^_Y)E!RSP^59I8K>=OO3;DV=L,+\$[[O4L#:W[([;BR5DF*).P!
M2F;SXUF",/2U8/H^Y!I2JS0'%_*%38#I-/>&^#I7CS.>92"3VE@H7*Q@0EQ\
M6+("$X8OFO^<QU1@DG&LY@V"U6+A+\/)^B[V-[/!-A;5@4NS794@IUS`)GAQ
M/($GZ/=^<'@$;>O2#?)<^%*6++VGT$IDB:TQ08-[,M:5R:=*!Y4VV)/06:9M
M528IOG##SU,E([Y[B^<Z=J7NL#E/1;\7**$THK&@'1%)+=.&0^.=8^5AKBJ=
M\;WK@L/'V(C3`HP7A)1>UF.ATON$_P)O=';^*K2R.2#"T443GU4'>'UW.OKX
METL71SQ77'X^"T&`A6XNLY)+L&[IDJ<J@X@;>\6T)(QKD(@R`;&2HJ9M47"3
M5\7.1"IUTO$&[Z)5X$=W?AR'_L8?;+_.YDDT6?=[I=O6CAG(^+^721N!0!4%
M2.M(6ZHU:&"9YS=2FR$@I6MJ/3](I1U"6OE$LIV`C'*^5QPG=9J;/+'4+IAM
MU(>%2Z:A25Q#F:`,W.Q+>'2[B[4Z:#"FE?U<\KET,5:@JKU/B*&$E#/1Z&.A
M'H"0>D1S%@AE(%0HF].&==?.AIH_H+#?$U<TR93+S"F1$#67Y(K+,D5N*+6)
M39Y*I>TQ.J;<5"/;N#)6MV8\^^,F02>BATFX&._W;@3L+=K9>37]LFW\YPL1
M@F6\<6P[$#G%:Y(TF?U_LS`O8K6J*-$-,&9Z^#P-,K%3;@.5)B)).&PW0]S0
MF<Q6!E/<FR*+N'3J^@9UYYC38]VI8(Z\N41K[7&%7:![,'(?[6^HQD[NOW(=
MHRL*&!_HH]713%F!IZX)7C3'%HJC-B!JV\`SZK$2F:^UZDAKTG9,WW8E<B`>
MT;CM'X[\U=COG+`8TMNQ(6:^-<6"<7F"-]3A-U!+`0(4`!0``@`(`&R<]SKH
M/L*3\0(``*0%```*````````````(`````````!W:6YC;60N:6YI4$L%!@``
0```!``$`.````!D#````````
`
end
sum -r/size 27514/871

[karlchen]

Good morning, folks.

I have been using ThreadFindFirst=1 since the times when the default still was 0 and I have not had any crash on exit caused by ThreadFindFirst=1. [...] So there must be at minimum one other factor which is relevant and which in combination with ThreadFindFirst=1 may lead to crashes on exit.

I am afraid I have got to correct the number of 0 crashes on exit to 1 since 01:00 a.m. (METDST).

Windows XP Prof SP2, 32bit, ger
Total Commander 7.50 pb7
The machine is connected to my ISP via a DSL modem.

Possibly relevant factor:
5 minutes before I decided to call it quits and shut Windows down, the DSL line had broken down (for 30 minutes by the way).

Kind regards,
Karl

[ghisler(Author)]

And the crash address was?

[alm]

So far this crash on exit only occured on my Athlon 1400 system. On my C2D E6750 it did not happen yet, same counts for laptop with T7300 cpu in it.

[jy307@columbia.edu]

I can make an access violation happen almost every time by doing the following: I put a thumb drive into a usb port. I open total commander. I select the thumb drive. I then close tc without shutting down or removing the thumb drive. unfortunately I cannot make it happen every time, but the propensity for access violation associated with thumb drive file transfers is very high.

[karlchen]

Hello, Christian.

And the crash address was?

I am sorry, but I did not take a screenshot. - My fault, I know. - It looked much like the access violation reported by waelderer at the beginning of this thread.
Provided the same access violation on exit occurs again I will take a screenshot.

By the way, the machine is a single core machine. No OODefrag monitoring in the background.

Kind regards,
Karl

[karlchen]

I can make an access violation happen almost every time by doing the following: I put a thumb drive into a usb port. I open total commander. I select the thumb drive. I then close tc without shutting down or removing the thumb drive.

Cannot confirm this. So far I have not experienced any relation to my USB stick on any of my machines:
+ Pentium III, single core, Windows XP Prof SP2, 32bit
+ Intel DualCore, Windows XP Prof SP2, 32bit
+ Intel QuadCore, Windows Vista Home Premium, 32bit
all using T.C 7.50 pb7

Karl

[ouzoWTF]

Got an access violation too when closing tcmd a moment ago.

Exception EAccessViolation in module TOTALCMD.EXE at 000648E1.
Access violation at address 00465B0D. Write of address 00E000BD.


I'm using WinXP SP3 and pb7.

[Boofo]

I am also using WinXP SP3 (32-bit) and pb7 and do not get any errors on close. I have a single core system (P4 2.8 GHZ from the stone-age).

[petermad]

2jy307@columbia.edu

but the propensity for access violation associated with thumb drive file transfers is very high.

If you have CopyCompatUsbSticks=0 in the [Configuration] section of your wincmd.ini file then try removing that.

[ghisler(Author)]

CopyCompatUsbSticks only has an effect when you COPY from or to an USB stick.

Unfortunately I couldn't reproduce the error so far, but at least I know where it occurs, so I can try to write a workaround...

[petermad]

but the propensity for access violation associated with thumb drive file transfers is very high.

CopyCompatUsbSticks only has an effect when you COPY from or to an USB stick.

Sorry, I thought that file transfer would be the same as copying.

[karlchen]

Hello, Christian.

And the crash address was?

I was lucky enough to be able to reproduce the crash on exit.

Same machine, same network error preceding the crash on exit. (Which is why I assume the network problem may be relevant.)

T.C. 7.50pb7 was running. The USB stick had been put in. (But this has never had any effect for me.) Tried to open my DSL connection (but had forgotten to put in the network cable). So I pressed the Cancel button in the "Connecting ..." dialogue box.
Next, I shutdown Total Commander 7.50 pb7.

Received this crash on exit message by Windows:

Application Error
Exception EAccessViolation in module TOTALCMD.EXE at 000648E1.
Access violation at address 00465B0D. Write of address 0157AFF9.

Windows XP Prof SP2, 32bit
Total Commander 7.50pb7
ThreadFindFirst=1 is active
As the DSL connection is an internet connection T.C. will never have any access to any network shares via UNC pathnames or via mapped drive letters.

Such a crash on exit has never occurred in cases
+ when the DSL connection had not been opened, yet
+ when the DSL connection had been terminated properly.

HTH,
Karl