Access violation when calling synchronization tool in separate process

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

Moderators: sheep, Hacker, Stefan2, white

Post Reply
Lolly-Bob
Junior Member
Junior Member
Posts: 18
Joined: 2015-09-01, 15:09 UTC

Access violation when calling synchronization tool in separate process

Post by *Lolly-Bob » 2018-08-29, 14:48 UTC

Hi,

up to version 9.20, the synchronization tool could be started in a separate process. Since version 9.21 you get an intercepted access violation. I start it with a button in the button bar.

Command: C:\TotalCmd\TOTALCMD64.EXE
Parameters: /S=S "%X%P" "%X%T"

The following window appears immediately:

https://xqxaja.bn.files.1drv.com/y4m_KMnh1NauwDNSLyNM25dAopk7wwcWEuUgNJFmHXBFTU_7zQooe5QkmMvEDPhIqXeDMM97RkYTRZ2Dw0vijWkW1ortVM-pzsH2I-pKT5RJIrJZo1rxavId8Q ... lation.png

The cm_FileSync command works.

Best regards

User avatar
Horst.Epp
Power Member
Power Member
Posts: 3470
Joined: 2003-02-06, 17:36 UTC
Location: Germany

Re: Access violation when calling synchronization tool in separate process

Post by *Horst.Epp » 2018-08-29, 15:18 UTC

No confirmed here.
I do this many times and it still works in the actual TC (x86 and x64) without any problems.
May be you have some special dirs the parameters are pointing to ?
Windows 10 Home x64 November 2019 Update, Version 1909 (OS Build 18363.476)
Intel(R) Core(TM) i7-4770 CPU @ 3.40GH, 16GB RAM
TC 9.50ß8 x64 / x86, Everything 1.4.1.958 (x64)

Lolly-Bob
Junior Member
Junior Member
Posts: 18
Joined: 2015-09-01, 15:09 UTC

Re: Access violation when calling synchronization tool in separate process

Post by *Lolly-Bob » 2018-08-29, 19:45 UTC

I just noticed that I only have this problem under Windows 8.1 Home 64bit, not under Windows 10 Pro 64bit.
It doesn't matter which directories I compare.

User avatar
Horst.Epp
Power Member
Power Member
Posts: 3470
Joined: 2003-02-06, 17:36 UTC
Location: Germany

Re: Access violation when calling synchronization tool in separate process

Post by *Horst.Epp » 2018-08-29, 19:48 UTC

Lolly-Bob wrote:
2018-08-29, 19:45 UTC
I just noticed that I only have this problem under Windows 8.1 Home 64bit, not under Windows 10 Pro 64bit.
It doesn't matter which directories I compare.
A good reason to update to Windows 10 :)
Its still for free and much better as 8.1
May be Christian has some idea.
Windows 10 Home x64 November 2019 Update, Version 1909 (OS Build 18363.476)
Intel(R) Core(TM) i7-4770 CPU @ 3.40GH, 16GB RAM
TC 9.50ß8 x64 / x86, Everything 1.4.1.958 (x64)

User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 38384
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Re: Access violation when calling synchronization tool in separate process

Post by *ghisler(Author) » 2018-08-30, 10:16 UTC

Thanks for your report. It's caused by the "prevent scrollbar crash" function, which should prevent another crash from happening on Windows 8.1.

You can disable this:
wincmd.ini, under [Configuration], please add:
PreventScrollbarCrash=0

However, Lister will crash again after calling it a few times when you set this.
Solution: Make a copy of your wincmd.ini, e.g. named synctool.ini, put PreventScrollbarCrash=0 only in that copy, and then start the standalone sync tool like this:
totalcmd64.exe /S=S /i=c:\totalcmd\synctool.ini "%X%P" "%X%T"
Author of Total Commander
http://www.ghisler.com

Lolly-Bob
Junior Member
Junior Member
Posts: 18
Joined: 2015-09-01, 15:09 UTC

Re: Access violation when calling synchronization tool in separate process

Post by *Lolly-Bob » 2018-08-30, 12:29 UTC

Thank you very much. It works.

User avatar
petermad
Power Member
Power Member
Posts: 8964
Joined: 2003-02-05, 20:24 UTC
Location: Valsted, Denmark
Contact:

Re: Access violation when calling synchronization tool in separate process

Post by *petermad » 2018-08-30, 17:16 UTC

2Lolly-Bob
Command: C:\TotalCmd\TOTALCMD64.EXE
Parameters: /S=S "%X%P" "%X%T"

You don't have to repeat %X - /S=S %X "%P" "%T" will do the same
Help wrote:%X Interprets the following parameters after this parameter as left/right instead of source/target:
and it is cancelled again with:
HElp wrote:%x Interprets the following parameters after this parameter again as source/target
License #524 (1994)
Danish Total Commander Translator
TC 9.5b3 32+64bit on Win XP 32bit, Win 7, 8.1 & 10 (1909) 64bit, 'Everything' 1.4.1.935 (x64)
TC 3.0b12 on Android 6.0
Get: Extended Total Commander Menus | PHSM-Calendar

Lolly-Bob
Junior Member
Junior Member
Posts: 18
Joined: 2015-09-01, 15:09 UTC

Re: Access violation when calling synchronization tool in separate process

Post by *Lolly-Bob » 2018-08-31, 11:46 UTC

Thank you, petermad, good to know.

browny
Member
Member
Posts: 191
Joined: 2007-09-10, 13:19 UTC

Re: Access violation when calling synchronization tool in separate process

Post by *browny » 2018-09-04, 08:17 UTC

Horst.Epp wrote:
2018-08-29, 19:48 UTC
A good reason to update to Windows 10
This issue could not be a reason to update.

Access violation occurs in Windows Server 2016, TC 9.21a.
If Ok button was pressed, the same dialog appears again, and next Ok causes crash.

User avatar
Horst.Epp
Power Member
Power Member
Posts: 3470
Joined: 2003-02-06, 17:36 UTC
Location: Germany

Re: Access violation when calling synchronization tool in separate process

Post by *Horst.Epp » 2018-09-04, 09:59 UTC

browny wrote:
2018-09-04, 08:17 UTC
Horst.Epp wrote:
2018-08-29, 19:48 UTC
A good reason to update to Windows 10
This issue could not be a reason to update.

Access violation occurs in Windows Server 2016, TC 9.21a.
If Ok button was pressed, the same dialog appears again, and next Ok causes crash.
You didn't mention Windows Server 2016 until this newest post
You said "I just noticed that I only have this problem under Windows 8.1 Home 64bit"
And this is definitely a reason to update to Windows 10 as long as it is free.
Windows 10 Home x64 November 2019 Update, Version 1909 (OS Build 18363.476)
Intel(R) Core(TM) i7-4770 CPU @ 3.40GH, 16GB RAM
TC 9.50ß8 x64 / x86, Everything 1.4.1.958 (x64)

Lolly-Bob
Junior Member
Junior Member
Posts: 18
Joined: 2015-09-01, 15:09 UTC

Re: Access violation when calling synchronization tool in separate process

Post by *Lolly-Bob » 2018-09-04, 12:35 UTC

Horst.Epp wrote:
2018-09-04, 09:59 UTC
You didn't mention Windows Server 2016 until this newest post
You mix something up, Horst.Epp. I'm Lolly-Bob, the initiator of this thread, but browny talked about Windows Server 2016.

User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 38384
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Re: Access violation when calling synchronization tool in separate process

Post by *ghisler(Author) » 2019-02-28, 08:28 UTC

This should be fixed in Total Commander 9.22 rc1 even with PreventScrollbarCrash=1 now. Please test!
Author of Total Commander
http://www.ghisler.com

Lolly-Bob
Junior Member
Junior Member
Posts: 18
Joined: 2015-09-01, 15:09 UTC

Re: Access violation when calling synchronization tool in separate process

Post by *Lolly-Bob » 2019-02-28, 11:06 UTC

The 9.22 rc1 x64 Version works on Windows 8.1 Home 64-bit. I can start the synchronization tool with or without PreventScrollbarCrash is set. But I don't know the lister scrollbar problem. I didn't had this problem.

Thank you.

Post Reply