+[8.50b2] "Separate Search Process" crashs with TC
Moderators: Hacker, petermad, Stefan2, white
+[8.50b2] "Separate Search Process" crashs with TC
My Environment:
Win8 64Bit
Tested with TCMD 32 and 64 Bit.
TCMD 32Bit works fine and does not crash.
Steps to reproduce:
1) Start TCMD 64Bit
2) Open "Search in separate process"
3) Perform a search to fill the "search results" box below.
4) click on "feed to listbox"
Observed behavior:
The new "search process" / "search window" crashs!
Thanks,
Ferhat
Win8 64Bit
Tested with TCMD 32 and 64 Bit.
TCMD 32Bit works fine and does not crash.
Steps to reproduce:
1) Start TCMD 64Bit
2) Open "Search in separate process"
3) Perform a search to fill the "search results" box below.
4) click on "feed to listbox"
Observed behavior:
The new "search process" / "search window" crashs!
Thanks,
Ferhat
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
I can indeed reproduce it on Windows 8 only. It's the search process which crashes. I will test it in the debugger.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Unfortunately I can no longer reproduce this error on Windows 8. Are you still able to reproduce it with beta 3? If yes, can you post the crash message, please?
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
@ghisler
I have installed Beta 3 right now and tested it again.
I have done exactly the same steps described above.
After clicking on "Feed to listbox" the process crashes again. I am getting the typical windows crash dialog: "Total Commander has stopped working"
I am missing here the typical TC crash dialog with stack trace information. This looks like an unhandled exception which kills the process.
Here is some info from my windows eventlog:
Faulting application name: TOTALCMD64.EXE, version: 8.5.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007fa00000008
Faulting process id: 0x11d0
Faulting application start time: 0x01ceae487bd93fbd
Faulting application path: D:\Application\totalcmd\TOTALCMD64.EXE
Faulting module path: unknown
Report Id: bc469807-1a3b-11e3-beee-00040ec695b2
Faulting package full name:
Faulting package-relative application ID:
I have installed Beta 3 right now and tested it again.
I have done exactly the same steps described above.
After clicking on "Feed to listbox" the process crashes again. I am getting the typical windows crash dialog: "Total Commander has stopped working"
I am missing here the typical TC crash dialog with stack trace information. This looks like an unhandled exception which kills the process.
Here is some info from my windows eventlog:
Faulting application name: TOTALCMD64.EXE, version: 8.5.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007fa00000008
Faulting process id: 0x11d0
Faulting application start time: 0x01ceae487bd93fbd
Faulting application path: D:\Application\totalcmd\TOTALCMD64.EXE
Faulting module path: unknown
Report Id: bc469807-1a3b-11e3-beee-00040ec695b2
Faulting package full name:
Faulting package-relative application ID:
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Hmm, address 7fa00000008 isn't in my code - difficult to say what that is without a stack trace.
Can you try this please: When you see the Windows crash dialog, don't close it. Instead open a second copy of Total Commander and go to the TEMP directory:
cd %TEMP%
There, look for a file with extension .mdmp or .dmp. It may be inside a ZIP or CAB file with the current date and time, ready to be sent to Microsoft Winqual. If you find this file copy it elsewhere because it will be deleted when you confirm the crash dialog.
Then please send this file to support at ghisler dot com, I can analyze it with windbg. It will (hopefully) contain a meaningful crash dump...
Can you try this please: When you see the Windows crash dialog, don't close it. Instead open a second copy of Total Commander and go to the TEMP directory:
cd %TEMP%
There, look for a file with extension .mdmp or .dmp. It may be inside a ZIP or CAB file with the current date and time, ready to be sent to Microsoft Winqual. If you find this file copy it elsewhere because it will be deleted when you confirm the crash dialog.
Then please send this file to support at ghisler dot com, I can analyze it with windbg. It will (hopefully) contain a meaningful crash dump...
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
It's no longer necessary, I found it! You need to click with the mouse (or a finger on the touchscreen). There is no crash when I use the hotkey...
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Please, can you check whether you still get this crash? Should be fixed for more than a month now...
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact: