Fixed - TC10 beta8: Crash after closing "Search in separate process" UI

Bug reports will be moved here when the described bug has been fixed

Moderators: white, Hacker, petermad, Stefan2

Post Reply
Slavic
Senior Member
Senior Member
Posts: 290
Joined: 2006-02-26, 15:41 UTC
Location: Montenegro

Fixed - TC10 beta8: Crash after closing "Search in separate process" UI

Post by *Slavic »

1. Open the dialog "Search in separate process" using either the Commands menu or combination Alt+Shift+F7
2. Press Esc key to close this UI.
3. Total Commander has stopped working. Problem signature: Problem event name: BEX64 etc etc...

In my TC configuration this bug is always reproduced.

Details from the Event Viewer
Faulting application name: TOTALCMD64.EXE, version: 10.0.0.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 6.3.9600.19994, time stamp: 0x60653cd2
Exception code: 0xc0000409
Fault offset: 0x000000000009016a
Faulting process ID: 0x7d0
Faulting application start time: 0x01d73dfb227b8bb9
Faulting application path: C:\Program Files\Totalcmd\TOTALCMD64.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Last edited by Slavic on 2021-05-06, 18:32 UTC, edited 1 time in total.
Desktop: Windows 11 Pro 23H2, TC 11.03(RC). Mobile: Pixel 5a, Android 14, TC 3.42b5
User avatar
tuska
Power Member
Power Member
Posts: 3740
Joined: 2007-05-21, 12:17 UTC

Re: TC10 beta8: Crash after closing "Search in separate process" UI

Post by *tuska »

2Slavic
Thank you, I can confirm the error regarding points 1. and 2.!

I recently opened the folder with the error reports under C:\ProgramData\Microsoft\Windows\WER\ReportArchive\
after a long time and wondered what had already accumulated there regarding TC.

The error only occurs in the x64 version!
However, I was able to continue using the x64 version afterwards without any problems.


Windows 10 Pro (x64) Version 20H2 (OS build 19042.964)  |  TC 10.00b8 x64
User avatar
Horst.Epp
Power Member
Power Member
Posts: 6450
Joined: 2003-02-06, 17:36 UTC
Location: Germany

Re: TC10 beta8: Crash after closing "Search in separate process" UI

Post by *Horst.Epp »

Confirmed for 1 and 2
But I can continue to work.

Here the WER report

Code: Select all

Version=1
EventType=APPCRASH
EventTime=132643309647559388
ReportType=2
Consent=1
UploadTime=132643309650384156
ReportStatus=268435456
ReportIdentifier=1bdedbf4-5ccb-4afc-92f8-9cc9e9a1a861
IntegratorReportIdentifier=122f6062-2a9a-4ea4-b24c-b6f2fa62caf2
Wow64Host=34404
NsAppName=totalcmd64.exe
OriginalFilename=totalcmd64.exe
AppSessionGuid=00004a00-0005-0071-595b-7327633ed701
TargetAppId=W:000680b7f1845d1193139b4b5a4588fa2de400000904!0000e07da374aa2012a0bc565470a8771e38f64c0df1!totalcmd64.exe
TargetAppVer=1970//01//01:00:00:00!964854!totalcmd64.exe
BootId=4294967295
TargetAsId=8386
UserImpactVector=808452912
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=7b8eebf35e0ac5eff4bde1c9ec716eb9
Response.BucketTable=4
Response.LegacyBucketId=1494598908728405689
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=totalcmd64.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=00000000
Sig[3].Name=Fault Module Name
Sig[3].Value=USER32.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.19041.906
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=efa6b327
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000000000005972c
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.19042.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=8192
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=c1ad
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=c1addfadf80d1787bc07ca5ab9c81966
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=36e6
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=36e62697e45eeeb7e548f4d3498d0341
UI[2]=C:\Tools\Wincmd\totalcmd64.exe
LoadedModule[0]=C:\Tools\Wincmd\totalcmd64.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\System32\advapi32.dll
LoadedModule[5]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[6]=C:\WINDOWS\System32\sechost.dll
LoadedModule[7]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[8]=C:\WINDOWS\System32\comdlg32.dll
LoadedModule[9]=C:\WINDOWS\System32\combase.dll
LoadedModule[10]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.844_none_ca00b6081b84eb1d\comctl32.dll
LoadedModule[11]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[12]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[13]=C:\WINDOWS\System32\shcore.dll
LoadedModule[14]=C:\WINDOWS\System32\USER32.dll
LoadedModule[15]=C:\WINDOWS\System32\win32u.dll
LoadedModule[16]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[17]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[18]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[19]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[20]=C:\WINDOWS\System32\ole32.dll
LoadedModule[21]=C:\WINDOWS\System32\oleaut32.dll
LoadedModule[22]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[23]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[24]=C:\WINDOWS\system32\winsta.dll
LoadedModule[25]=C:\WINDOWS\system32\sspicli.dll
LoadedModule[26]=C:\WINDOWS\system32\version.dll
LoadedModule[27]=C:\WINDOWS\system32\winmm.dll
LoadedModule[28]=C:\WINDOWS\system32\mpr.dll
LoadedModule[29]=C:\WINDOWS\system32\dwmapi.DLL
LoadedModule[30]=C:\WINDOWS\system32\winspool.drv
LoadedModule[31]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[32]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\windows.storage.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\Wldp.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
LoadedModule[36]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\profapi.dll
LoadedModule[38]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[39]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[40]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\Uiautomationcore.dll
LoadedModule[42]=C:\WINDOWS\SYSTEM32\TextShaping.dll
LoadedModule[43]=C:\WINDOWS\SYSTEM32\textinputframework.dll
LoadedModule[44]=C:\WINDOWS\System32\CoreUIComponents.dll
LoadedModule[45]=C:\WINDOWS\System32\CoreMessaging.dll
LoadedModule[46]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[48]=C:\WINDOWS\SYSTEM32\wintypes.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=19042
OsInfo[3].Key=ubr
OsInfo[3].Value=928
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=94
OsInfo[8].Key=sku
OsInfo[8].Value=101
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=768
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=221069485
OsInfo[15].Key=osinsty
OsInfo[15].Value=1
OsInfo[16].Key=iever
OsInfo[16].Value=11.789.19041.0-11.0.1000
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16211
OsInfo[19].Key=svolsz
OsInfo[19].Value=220
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=191206
OsInfo[22].Key=bldtm
OsInfo[22].Value=1406
OsInfo[23].Key=bldbrch
OsInfo[23].Value=vb_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.19041.928.amd64fre.vb_release.191206-1406
OsInfo[30].Key=buildflightid
OsInfo[30].Value=5AFFFB9B-FB87-4242-B66A-4ECEEB1CF75F.1
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[34].Key=fconid
OsInfo[35].Key=containerid
OsInfo[36].Key=containertype
OsInfo[37].Key=edu
OsInfo[37].Value=0
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Total Commander
AppPath=C:\Tools\Wincmd\totalcmd64.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=5BA6D3B30D3B19C821AF5FCD2C4BDD18
MetadataHash=23442063
Windows 11 Home x64 Version 23H2 (OS Build 22631.3374)
TC 11.03 x64 / x86
Everything 1.5.0.1371a (x64), Everything Toolbar 1.3.2, Listary Pro 6.3.0.69
QAP 11.6.3.2 x64
User avatar
petermad
Power Member
Power Member
Posts: 14739
Joined: 2003-02-05, 20:24 UTC
Location: Denmark
Contact:

Re: TC10 beta8: Crash after closing "Search in separate process" UI

Post by *petermad »

I cannot reproduce this in under neither Windows 7 nor Windows 10 with TC 10 b8 x64

I recently opened the folder with the error reports under C:\ProgramData\Microsoft\Windows\WER\ReportArchive\
after a long time and wondered what had already accumulated there regarding TC.
I checked too - under windows 7 I had no error reports for TC, under Windows 10 I had 133 reports since March 20 - two of then for totalcmd.exe the rest for totalcmd64.exe. Notice, I don't use Windows 10 very much.

A new report turned up in Windows 10 while I was testing this - but I encountered no error messages.

Code: Select all

Version=1
EventType=APPCRASH
EventTime=132643446466700337
ReportType=2
Consent=1
UploadTime=132643446476856034
ReportStatus=268435456
ReportIdentifier=60072416-3973-4b13-91c5-29c13dc2c313
IntegratorReportIdentifier=187f54d0-3a97-413a-a921-e977179a1056
Wow64Host=34404
NsAppName=TOTALCMD64.EXE
OriginalFilename=totalcmd64.exe
AppSessionGuid=00000a60-0001-002c-d533-6f00833ed701
TargetAppId=W:000680b7f1845d1193139b4b5a4588fa2de400000904!0000e07da374aa2012a0bc565470a8771e38f64c0df1!TOTALCMD64.EXE
TargetAppVer=1970//01//01:00:00:00!964854!TOTALCMD64.EXE
BootId=4294967295
TargetAsId=1911
UserImpactVector=808452912
IsFatal=1
EtwNonCollectReason=4
Response.BucketId=7b8eebf35e0ac5eff4bde1c9ec716eb9
Response.BucketTable=4
Response.LegacyBucketId=1494598908728405689
Response.type=4
Sig[0].Name=Programnavn
Sig[0].Value=TOTALCMD64.EXE
Sig[1].Name=Programversion
Sig[1].Value=10.0.0.0
Sig[2].Name=Tidsstempel for program
Sig[2].Value=00000000
Sig[3].Name=Fejlmodulnavn
Sig[3].Value=USER32.dll
Sig[4].Name=Fejlmodulversion
Sig[4].Value=10.0.19041.906
Sig[5].Name=Tidsstempel for fejlmodul
Sig[5].Value=efa6b327
Sig[6].Name=Undtagelseskode
Sig[6].Value=c0000005
Sig[7].Name=Undtagelsesforskydning
Sig[7].Value=000000000005972c
DynamicSig[1].Name=OS-version
DynamicSig[1].Value=10.0.19042.2.0.0.768.101
DynamicSig[2].Name=Landestandard-id
DynamicSig[2].Value=1030
DynamicSig[22].Name=Flere oplysninger 1
DynamicSig[22].Value=c1ad
DynamicSig[23].Name=Flere oplysninger 2
DynamicSig[23].Value=c1addfadf80d1787bc07ca5ab9c81966
DynamicSig[24].Name=Flere oplysninger 3
DynamicSig[24].Value=36e6
DynamicSig[25].Name=Flere oplysninger 4
DynamicSig[25].Value=36e62697e45eeeb7e548f4d3498d0341
UI[2]=C:\totalcmd\TOTALCMD64.EXE
LoadedModule[0]=C:\totalcmd\TOTALCMD64.EXE
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\SYSTEM32\apphelp.dll
LoadedModule[5]=C:\WINDOWS\SYSTEM32\AcGenral.DLL
LoadedModule[6]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[7]=C:\WINDOWS\System32\sechost.dll
LoadedModule[8]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[9]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[10]=C:\WINDOWS\System32\USER32.dll
LoadedModule[11]=C:\WINDOWS\System32\win32u.dll
LoadedModule[12]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[13]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[14]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[15]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[16]=C:\WINDOWS\System32\ole32.dll
LoadedModule[17]=C:\WINDOWS\System32\combase.dll
LoadedModule[18]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[19]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[20]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[21]=C:\WINDOWS\SYSTEM32\MPR.dll
LoadedModule[22]=C:\WINDOWS\SYSTEM32\SspiCli.dll
LoadedModule[23]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[24]=C:\WINDOWS\System32\comdlg32.dll
LoadedModule[25]=C:\WINDOWS\System32\shcore.dll
LoadedModule[26]=C:\WINDOWS\System32\oleaut32.dll
LoadedModule[27]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.844_none_ca00b6081b84eb1d\comctl32.dll
LoadedModule[28]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[29]=C:\WINDOWS\system32\winsta.dll
LoadedModule[30]=C:\WINDOWS\system32\version.dll
LoadedModule[31]=C:\WINDOWS\system32\winmm.dll
LoadedModule[32]=C:\WINDOWS\system32\dwmapi.DLL
LoadedModule[33]=C:\WINDOWS\system32\winspool.drv
LoadedModule[34]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[35]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[36]=C:\WINDOWS\SYSTEM32\windows.storage.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\Wldp.dll
LoadedModule[38]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
LoadedModule[39]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\profapi.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[42]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[43]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\Uiautomationcore.dll
LoadedModule[45]=C:\WINDOWS\SYSTEM32\TextShaping.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\textinputframework.dll
LoadedModule[47]=C:\WINDOWS\System32\CoreUIComponents.dll
LoadedModule[48]=C:\WINDOWS\System32\CoreMessaging.dll
LoadedModule[49]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[50]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[51]=C:\WINDOWS\SYSTEM32\wintypes.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=19042
OsInfo[3].Key=ubr
OsInfo[3].Value=928
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1030
OsInfo[7].Key=geoid
OsInfo[7].Value=61
OsInfo[8].Key=sku
OsInfo[8].Value=101
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=768
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=221069712
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.789.19041.0-11.0.1000
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=7778
OsInfo[19].Key=svolsz
OsInfo[19].Value=456
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=191206
OsInfo[22].Key=bldtm
OsInfo[22].Value=1406
OsInfo[23].Key=bldbrch
OsInfo[23].Value=vb_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.19041.928.amd64fre.vb_release.191206-1406
OsInfo[30].Key=buildflightid
OsInfo[30].Value=a9f63563-9881-4bdd-951c-0db5007fc061
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[33].Value=RD:2685
OsInfo[34].Key=fconid
OsInfo[35].Key=containerid
OsInfo[36].Key=containertype
OsInfo[37].Key=edu
OsInfo[37].Value=0
FriendlyEventName=Handlingen blev afbrudt
ConsentKey=APPCRASH
AppName=Total Commander
AppPath=C:\totalcmd\TOTALCMD64.EXE
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=293B39198A4AE063285C1D27AF4AE558
MetadataHash=601353612
EDIT: I tested TC 10 b8 32bit under Windows 10, and opening and closing the separate Find files dialog, does not generate an error report with 32bit TC.

If it can be of any help, I have uploaded all my Windows 10 error reports from C:\ProgramData\Microsoft\Windows\WER\ReportArchive\ here: https://madsenworld.dk/tcmd/ReportArchive.zip
License #524 (1994)
Danish Total Commander Translator
TC 11.03 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1371a
TC 3.50b4 on Android 6 & 13
Try: TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48021
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Re: TC10 beta8: Crash after closing "Search in separate process" UI

Post by *ghisler(Author) »

The problem happens because I unload the OLE library via OleUnInitialize while there are still active OLE objects. I think i found a wy now to prevent that, at least the errors are gone now. It's caused by the Delphi/Lazarus finalization sections which are called in arbitrary order, so the one unloading the OLE library is called too early.
Author of Total Commander
https://www.ghisler.com
Slavic
Senior Member
Senior Member
Posts: 290
Joined: 2006-02-26, 15:41 UTC
Location: Montenegro

Re: TC10 beta8: Crash after closing "Search in separate process" UI

Post by *Slavic »

petermad wrote: 2021-05-01, 12:17 UTC A new report turned up in Windows 10 while I was testing this - but I encountered no error messages.
Does this mean that Windows 10 can hide the crashes from a user, keeping information only in the logs? I don't think it's a good design, even when the crash is recoverable, like this case. It would be good if this setting is available to user and can be returned back to show such events.
Desktop: Windows 11 Pro 23H2, TC 11.03(RC). Mobile: Pixel 5a, Android 14, TC 3.42b5
User avatar
tuska
Power Member
Power Member
Posts: 3740
Joined: 2007-05-21, 12:17 UTC

Re: TC10 beta8: Crash after closing "Search in separate process" UI

Post by *tuska »

HISTORY.TXT wrote:06.05.21 Release Total Commander 10.00 public beta 9
01.05.01 Fixed: Silent access violation (in event viewer) when closing standalone search dialog,
                because OleUnInitialize was called while there were still some OLE objects (64)
Thank you!
This is fixed! :)


Windows 10 Pro (x64) Version 20H2 (OS build 19042.964) | TC 10.00b9 x64/x86
Slavic
Senior Member
Senior Member
Posts: 290
Joined: 2006-02-26, 15:41 UTC
Location: Montenegro

Re: Fixed - TC10 beta8: Crash after closing "Search in separate process" UI

Post by *Slavic »

Fixed in beta 9. After a number of tests, Search in separate process combined with simple Search, I haven't seen any crash. Thanks!
Desktop: Windows 11 Pro 23H2, TC 11.03(RC). Mobile: Pixel 5a, Android 14, TC 3.42b5
User avatar
petermad
Power Member
Power Member
Posts: 14739
Joined: 2003-02-05, 20:24 UTC
Location: Denmark
Contact:

Re: Fixed - TC10 beta8: Crash after closing "Search in separate process" UI

Post by *petermad »

I no longer get error reports in C:\ProgramData\Microsoft\Windows\WER\ReportArchive\ when I close a separate Find files dialog under TC 10 b9 x64 under Windows 10 :-)
License #524 (1994)
Danish Total Commander Translator
TC 11.03 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1371a
TC 3.50b4 on Android 6 & 13
Try: TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
Post Reply