Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

How to deal with "Script stopped responding" in general Part 3

  • No replies
  • 2 have this problem
  • 7 views
more options

OK, I have asked about this issue before, and am back because it won't go away.

First, I have tried resetting Firefox. Yesterday was the most recent time.

I have tried using add-on Script Blockers.

The Script Blocker program worked for a while. The problem is that the primary source of the script problems are Hotmail and Gmail, and I need to have these functioning and open. Plus it is not easy to determine what a script does before deciding to let it in.

So I'm going to start from the computer user perspective: Why does this happen at all?

I understand the need for scripts to be used for websites to function. What I don't understand is why my entire computer slows to a crawl, some programs get cut off entirely, and then I have to try to figure out what webpage is causing the problem...slowly. Even when I click the box to stop the script, my computer is still incredibly slow for an unreasonable amount of time. By unreasonable amount, I mean that it is so long that I can't even close Firefox within 5 minutes just to make it stop. By unreasonable amount, I mean I have actually just set my computer to restart so that Firefox will be forced closed and then cancel the restart when Firefox shuts down.

What can Hotmail, Gmail, or any other program be doing that is of sufficient importance that it can essentially take over the computer? Nothing that isn't critical to the functioning of the computer should have this power. There is nothing critical about a script on Hotmail while I'm not even using that should let it take over all of the computer's resources. I would rather have Hotmail crash and shut off than have it let a script take over my computer. I can click on my Hotmail start up button within seconds while a script that won't respond might take 15 minutes to deal with.

So can someone please explain to me why this system exists? Why isn't there a command that says "a script may use up this amount of processing power only" that allows a person to keep using their computer while the script futily whirls away? Why isn't there a way to have an automatic setting like "let a script try to run for X seconds and if it doesn't work just stop it"? Why doesn't a window pop-up on the computer screen regardless of where the script problem is to alert you what webpage is causing the problem instead of making the user guess?

There doesn't even seem to be much purpose to the scripts. If I stop a script that is not responding on Hotmail, I can still use Hotmail when the computer recovers. So why does this happen?

This system seems insane to me. Honestly, I don't understand why scripts are allowed to do this. Can someone at least help with an explanation of why this happens? Why there isn't a way to make it stop? In a world of apps it seems like something that would kill non-responding scripts after a brief time would be a winner. How did we reach this chokepoint in computer functioning and why haven't we figured out how to stop it?

Thank you for any help, whether it be fixing the problem or just explaining the purpose.

OK, I have asked about this issue before, and am back because it won't go away. First, I have tried resetting Firefox. Yesterday was the most recent time. I have tried using add-on Script Blockers. The Script Blocker program worked for a while. The problem is that the primary source of the script problems are Hotmail and Gmail, and I need to have these functioning and open. Plus it is not easy to determine what a script does before deciding to let it in. So I'm going to start from the computer user perspective: Why does this happen at all? I understand the need for scripts to be used for websites to function. What I don't understand is why my entire computer slows to a crawl, some programs get cut off entirely, and then I have to try to figure out what webpage is causing the problem...slowly. Even when I click the box to stop the script, my computer is still incredibly slow for an unreasonable amount of time. By unreasonable amount, I mean that it is so long that I can't even close Firefox within 5 minutes just to make it stop. By unreasonable amount, I mean I have actually just set my computer to restart so that Firefox will be forced closed and then cancel the restart when Firefox shuts down. What can Hotmail, Gmail, or any other program be doing that is of sufficient importance that it can essentially take over the computer? Nothing that isn't critical to the functioning of the computer should have this power. There is nothing critical about a script on Hotmail while I'm not even using that should let it take over all of the computer's resources. I would rather have Hotmail crash and shut off than have it let a script take over my computer. I can click on my Hotmail start up button within seconds while a script that won't respond might take 15 minutes to deal with. So can someone please explain to me why this system exists? Why isn't there a command that says "a script may use up this amount of processing power only" that allows a person to keep using their computer while the script futily whirls away? Why isn't there a way to have an automatic setting like "let a script try to run for X seconds and if it doesn't work just stop it"? Why doesn't a window pop-up on the computer screen regardless of where the script problem is to alert you what webpage is causing the problem instead of making the user guess? There doesn't even seem to be much purpose to the scripts. If I stop a script that is not responding on Hotmail, I can still use Hotmail when the computer recovers. So why does this happen? This system seems insane to me. Honestly, I don't understand why scripts are allowed to do this. Can someone at least help with an explanation of why this happens? Why there isn't a way to make it stop? In a world of apps it seems like something that would kill non-responding scripts after a brief time would be a winner. How did we reach this chokepoint in computer functioning and why haven't we figured out how to stop it? Thank you for any help, whether it be fixing the problem or just explaining the purpose.