hello,
i'm working as a sysadmin with licensed salamander since 2000 and never got any problems.
But since today i have problems:
I always start salamander with "runas domain\admin-account" and mount a lot of network drives. ("normal" work with mailclient and webbrowser is running in
after i swap to a network drive the cpu-load is 100% (all used from salamand.exe) and my system (Windows XP sp2 with all patches) is not usable any more. Killing the salamander process via "sysinternals process explorer" needs about 5 minutes and all other programs are freezing in that time.
i have the same behaviour on my desktop and my laptop. it dosn't matter which server i connect to. i also reinstalled salamnder without success.
the only new thing on both systems are the actual Microsoft October patches from last week.
Am i the only person with problems?
rg. Borris
100% cpu load since today
-
- ALTAP Staff
- Posts: 5231
- Joined: 08 Dec 2005, 06:34
- Location: Novy Bor, Czech Republic
- Contact:
Hello Borris,
Please try this: start two instances of Salamander.
Freeze the first instance.
Switch to the second instance, from menu Help choose the Task List commad.
Select freezed instance, click the Break button.
Bug report should be displayed for freezed instance.
Please send it to my email jan.rysavy@altap.cz.
Btw, when you start Salamander as normal user, is it OK?
Could you reproduce this problem when you access your own shares using UNC path?
Please try this: start two instances of Salamander.
Freeze the first instance.
Switch to the second instance, from menu Help choose the Task List commad.
Select freezed instance, click the Break button.
Bug report should be displayed for freezed instance.
Please send it to my email jan.rysavy@altap.cz.
Btw, when you start Salamander as normal user, is it OK?
Could you reproduce this problem when you access your own shares using UNC path?
Hi Jan,
thanks for fast response.
I tried different szenarios now. The freeze always occurs with very large xml-files (>150 MB). But with windows-explorer i have the same freeze.
So it seems to be a problem of our local AV-Software with large xml-files and not a problem of salamander. (on a test-system without AV i got no problemes)
sorry for probably false alarm. (salamander is the best
regards from germany borris
thanks for fast response.
I tried different szenarios now. The freeze always occurs with very large xml-files (>150 MB). But with windows-explorer i have the same freeze.
So it seems to be a problem of our local AV-Software with large xml-files and not a problem of salamander. (on a test-system without AV i got no problemes)
sorry for probably false alarm. (salamander is the best
regards from germany borris
-
- ALTAP Staff
- Posts: 5231
- Joined: 08 Dec 2005, 06:34
- Location: Novy Bor, Czech Republic
- Contact:
-
- Posts: 593
- Joined: 09 Dec 2005, 17:30
- Location: a step further
- Contact:
I have had the same problem. It's not in SS, it's in MS's XML parser.Anonymous wrote:I tried different szenarios now. The freeze always occurs with very large xml-files (>150 MB). But with windows-explorer i have the same freeze.
I've parsed 70MB XML and because the IE/XML Viewer runs in SS context, when it freezes, the SS window seems to be dead to.
Jiri {x2} Cincura
-
- ALTAP Staff
- Posts: 5231
- Joined: 08 Dec 2005, 06:34
- Location: Novy Bor, Czech Republic
- Contact:
-
- ALTAP Staff
- Posts: 5231
- Joined: 08 Dec 2005, 06:34
- Location: Novy Bor, Czech Republic
- Contact:
Please ask ESET http://www.eset.com/
Describe them how to reproduce this problem step by step.
You can probably reproduce this problem using Windows Explorer too?
Describe them how to reproduce this problem step by step.
You can probably reproduce this problem using Windows Explorer too?