This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

How can I close just one tab that has locked up rather than close the whole browser for being unresponsive?

  • 2 amsoshi
  • 3 sa na da wannan matsala
  • 326 views
  • Amsa ta ƙarshe daga FredMcD

more options

I have a bad habit of having multiple tabs open. If I click on a link which results in the entire browser becoming unresponsive, how can I close the offending tab rather than having to close the whole browser and loosing all my tabs?

I have a bad habit of having multiple tabs open. If I click on a link which results in the entire browser becoming unresponsive, how can I close the offending tab rather than having to close the whole browser and loosing all my tabs?

Mafitar da aka zaɓa

It's not a bad habit, it's normal.

Unfortunately, there currently is no way to "kill" a single tab without taking down Firefox.

A few times a week I get "not responding" when I exceed the amount of memory Firefox can use. Usually within 60-90 seconds I can shut down Firefox using the menu, either:

  • "3-bar" menu button > "power" button
  • (menu bar) File > Exit
  • pressing these keys in sequence: Alt f x

Freezes caused by other reasons might not release, in which case you're stuck. Prevention would be the best cure.

This support article covers some common reasons for freezes: Firefox hangs or is not responding - How to fix.

Since the Flash plugin also can cause this problem and it's used pervasively through the web, I suggest the following to minimize potential issues with Flash during your troubleshooting:

(1) To avoid unnecessary pain on sites where Flash is not actually essential, try setting Flash to Click-to-Play ("Ask to Activate"). This will delay Flash from starting on a page until you approve it.

To set "Ask to Activate", open the Add-ons page using either:

  • Ctrl+Shift+a
  • "3-bar" menu button (or Tools menu) > Add-ons

In the left column, click Plugins. Look for "Shockwave Flash" and change "Always Activate" to "Ask to Activate".

With this setting, when you visit a site that wants to use Flash, you should see a notification icon in the address bar and usually (but not always) one of the following: a link in a dark gray rectangle in the page or an infobar sliding down between the toolbar area and the page.

The plugin notification icon in the address bar typically looks like a small, dark gray Lego block. (If it's red, Flash needs updating.)

The delay in activating Flash can help distinguish between problems caused on initial page load, styling, and script activation vs. loading/running Flash.

If you see a good reason to use Flash, and the site looks trustworthy, you can go ahead and click the notification icon in the address bar to allow Flash. You can trust the site for the time being or permanently.

But some pages use Flash only for tracking or playing ads, so if you don't see an immediate need for Flash, feel free to ignore the notification! It will just sit there in case you want to use it later.

(2) A common cause of unresponsive script errors on Windows Vista and higher is the protected mode feature of the Flash player plugin. That feature has security benefits, but seems to have serious compatibility issues on some systems. You can disable it using the Add-ons page. Either:

  • Ctrl+Shift+a
  • "3-bar" menu button (or Tools menu) > Add-ons

In the left column, click Plugins. On the right side, find "Shockwave Flash" and click the More link. Then uncheck the box for "Enable Adobe Flash protected mode" and try that for a day to see whether it helps.

Karanta wannan amsa a matsayinta 👍 0

All Replies (2)

more options

Zaɓi Mafita

It's not a bad habit, it's normal.

Unfortunately, there currently is no way to "kill" a single tab without taking down Firefox.

A few times a week I get "not responding" when I exceed the amount of memory Firefox can use. Usually within 60-90 seconds I can shut down Firefox using the menu, either:

  • "3-bar" menu button > "power" button
  • (menu bar) File > Exit
  • pressing these keys in sequence: Alt f x

Freezes caused by other reasons might not release, in which case you're stuck. Prevention would be the best cure.

This support article covers some common reasons for freezes: Firefox hangs or is not responding - How to fix.

Since the Flash plugin also can cause this problem and it's used pervasively through the web, I suggest the following to minimize potential issues with Flash during your troubleshooting:

(1) To avoid unnecessary pain on sites where Flash is not actually essential, try setting Flash to Click-to-Play ("Ask to Activate"). This will delay Flash from starting on a page until you approve it.

To set "Ask to Activate", open the Add-ons page using either:

  • Ctrl+Shift+a
  • "3-bar" menu button (or Tools menu) > Add-ons

In the left column, click Plugins. Look for "Shockwave Flash" and change "Always Activate" to "Ask to Activate".

With this setting, when you visit a site that wants to use Flash, you should see a notification icon in the address bar and usually (but not always) one of the following: a link in a dark gray rectangle in the page or an infobar sliding down between the toolbar area and the page.

The plugin notification icon in the address bar typically looks like a small, dark gray Lego block. (If it's red, Flash needs updating.)

The delay in activating Flash can help distinguish between problems caused on initial page load, styling, and script activation vs. loading/running Flash.

If you see a good reason to use Flash, and the site looks trustworthy, you can go ahead and click the notification icon in the address bar to allow Flash. You can trust the site for the time being or permanently.

But some pages use Flash only for tracking or playing ads, so if you don't see an immediate need for Flash, feel free to ignore the notification! It will just sit there in case you want to use it later.

(2) A common cause of unresponsive script errors on Windows Vista and higher is the protected mode feature of the Flash player plugin. That feature has security benefits, but seems to have serious compatibility issues on some systems. You can disable it using the Add-ons page. Either:

  • Ctrl+Shift+a
  • "3-bar" menu button (or Tools menu) > Add-ons

In the left column, click Plugins. On the right side, find "Shockwave Flash" and click the More link. Then uncheck the box for "Enable Adobe Flash protected mode" and try that for a day to see whether it helps.

more options

This might help;

Restart {web link} "Restart" menu and button, with configurable shortcut key.


Restart Button {web link} Restart button for Firefox