WinSCP starts up EXTREMELY SLOWLY

I recently needed WinSCP (I only use it every few months) and discovered that it now starts EXTREMELY SLOWLY. Like two minutes or more between double-clicking the icon and seeing the WinSCP Login prompt. This was with a fairly recent 5.x beta and then with 4.3.8 as well. I was curious what was up and looked at the files/objects being used by WinSCP to see if I could tell why it was so darned slow and discovered these three that I cannot explain: In the folder C:\Program Files\Oracle\JavaFX 2.1 Runtime\lib the files deploy.jar, javaws.jar and plugin.jar are all in use. Is WinSCP written in Java? I suppose that would explain it. Perhaps Oracle's recent Java update broke (or almost broke?) something.

Thanks for your report.
I have sent you an email with a debug version of WinSCP to address you have used to register on this forum.

Btw, WinSCP does not use Java.

The debug WinSCP you provided is loading noticeably quicker, taking only about 46 seconds instead of two minutes or more as it had been doing. I've attached the log file it produced and, FWIW, my personal target (if it were my code I was debugging) would be these two lines:

[08:01:21.970] [1CF0] [PAS:0:unk] CustomDirView init
[08:02:00.611] [1CF0] [PAS:0:unk] TB2Version init >

The 39 second gap right there doesn't seem good to me.

Also, FYI, I asked about the Java because it seems that a few other programs (most notably, WinZip 14.0) are also loading much slower and the Java update is the only thing I've installed, other than critical Windows updates. So it seemed a likely choice, plus, for whatever reason, there ARE Java DLLs somehow attached to the WinSCP process, so maybe Oracle has done a virus-like thing and added Java in to the execution stream of EVERYTHING, whether needed or not.
-- I've added a report that I discovered Process Explorer could save that shows all of the DLLs associated with the WinSCP.exe process on my computer. I've checked several other programs (including some that I wrote) and they do not list any of the Java DLLs, but for some reason, WinSCP does include them -- I don't know why it is being selected for this "honor", but it is. So perhaps the slowness is whatever is connecting Java to WinSCP instead of WinSCP itself.[/i]

Thanks. I'll come back to you in few days.

hi,
does some body get a feedback ?

I'm using the latest version 5.08 build 2438
when I moved from previous version 5, I de-installed the old assembly and installed the new

I get a similar problem running winscp via .net&com from a csharp program
I get 2 differents result :
under windows 7 pro, the assembly is loading ok, no delay
under windows 2003 R2 serveur edition, it takes 1 minutes

I try to isolate the problem and this is just loading the assembly that takes 1 minutes
So, I put a function at the beginning of the program before using any .net classes
just this function takes 1 minutes on the windows 2003 server

Ant Idea? any reason ?
thanks,


private static int Preload_Winscp(bool lDEBUG)
{
try
{
Assembly SampleAssembly = Assembly.Load ("WinSCP, Version=1.0.0.725,
Culture=neutral, PublicKeyToken=b5f19f5762436b89");
return (0);
}
catch (Exception ex)
{
ex.Displaycatched("ERR:Preload:WinSCP assembly");
Console.WriteLine("INFO:Start process erreur :" + ex.StackTrace);
return (1);
}
}

nicis wrote:

I'm using the latest version 5.08 build 2438
when I moved from previous version 5, I de-installed the old assembly and installed the new

I get a similar problem running winscp via .net&com from a csharp program
I get 2 differents result :
under windows 7 pro, the assembly is loading ok, no delay
under windows 2003 R2 serveur edition, it takes 1 minutes
...

Thanks for your report.
I have sent you an email with a debug version of WinSCP to address you have used to register on this forum.

hi,

very strange behaviour

I remove winscp.dll via RegAsm.exe, copy your debug version and registred the dll again (sucessfully) but, when run my csharp application, get an error (cannot load the assembly 1.0.0.725 or any dependencies, name or codebase invalid, ...).

nevermind. so, I unregistred again the debug dll, copy the saved tools and registred again the non-debug version

and ... now, it's working. winscp is loading immediatly.

anyway, thanks for the debug version I did not use but solved my configuration problem