ShadowTech
I have no idea what causes this.. I have not been able to reproduce it on my own, but it has happened a couple times on my machine and just recently a friend had the same.
Common Machines:
AMD XP w/ Windows XP Pro (happened on 1600+, 2000+, 2500+, 2800+)
The problem:
SmartFTP is for some reason driving CPU usage to 100% and holds it there constantly. It is very rarely, but that doesn't make it any lesser a bug. The program will seem to still be running fine, so ya never notice, until you try to do something on your machine and notice it's very sluggish. This then leads to more serious problems. Like in the recent case with my friend that prompted me to post.
He let SmartFTP run on his system and went to watch TV. Came back and couldn't do anything on his machine. Since he told me what he was doing, I told him to check processes and sure enough there was smart sitting at 100%. So he then crashed the process but still suffered slowdowns. Leaving his system on, it eventually froze up and crashed. After rebooting, his crashes continued.. finally looking at his temps, the CPU was hitting 70+C.
So, the same thing that has happened to me, also happened to him, and a couple others I have talked to. The program locks up.. forces your cpu to work overtime.. drives up the heat, and if you have the generic thermal pads or cheap thermal paste on the cpu.. it melts. Once it is melted there is no way the cpu will stay cool until you replace it.
It is just ridiculous that a program can have a problem like this. Imagine if you left your machine transferring while you were sleeping and SmartFTP locked up like this.. by the time you woke up your cpu would be toast.
As I said, we have not been able to reproduce this error on purpose.. as it happens so rarely .. but in all instances it was while doing a drag and drop FXP between two site windows. Sorry I can't give you more details .. but it doesn't write anything to any errorlogs as the program doesn't "crash" .. but it is there! When it happened to me I thought maybe it was isolated.. but I know of at least 3 other people who have had it happen. There are probably more that just chalk it up to a wierd coincidence and never figure the program as the culprit.
Common Machines:
AMD XP w/ Windows XP Pro (happened on 1600+, 2000+, 2500+, 2800+)
The problem:
SmartFTP is for some reason driving CPU usage to 100% and holds it there constantly. It is very rarely, but that doesn't make it any lesser a bug. The program will seem to still be running fine, so ya never notice, until you try to do something on your machine and notice it's very sluggish. This then leads to more serious problems. Like in the recent case with my friend that prompted me to post.
He let SmartFTP run on his system and went to watch TV. Came back and couldn't do anything on his machine. Since he told me what he was doing, I told him to check processes and sure enough there was smart sitting at 100%. So he then crashed the process but still suffered slowdowns. Leaving his system on, it eventually froze up and crashed. After rebooting, his crashes continued.. finally looking at his temps, the CPU was hitting 70+C.
So, the same thing that has happened to me, also happened to him, and a couple others I have talked to. The program locks up.. forces your cpu to work overtime.. drives up the heat, and if you have the generic thermal pads or cheap thermal paste on the cpu.. it melts. Once it is melted there is no way the cpu will stay cool until you replace it.
It is just ridiculous that a program can have a problem like this. Imagine if you left your machine transferring while you were sleeping and SmartFTP locked up like this.. by the time you woke up your cpu would be toast.
As I said, we have not been able to reproduce this error on purpose.. as it happens so rarely .. but in all instances it was while doing a drag and drop FXP between two site windows. Sorry I can't give you more details .. but it doesn't write anything to any errorlogs as the program doesn't "crash" .. but it is there! When it happened to me I thought maybe it was isolated.. but I know of at least 3 other people who have had it happen. There are probably more that just chalk it up to a wierd coincidence and never figure the program as the culprit.