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

new tab appears at startup, cannot close

  • 5 replies
  • 5 have this problem
  • 5 views
  • Last reply by NickNackGus

more options

Occasionally, a new tab will open when starting Firefox in Windows 7 or Ubuntu 12.10. This opens to the default new tab page for Firefox, which I have set to about:blank. This tab cannot be closed by left clicking the "x", by right clicking and selecting close tab from the context menu, or with "Ctrl+W". Additionally, switching between tabs with "Ctrl+Tab" and "Ctrl+Shift+Tab" skips over this tab. It behaves as if it is already closed, but improperly. I suspect it MAY be because it was loaded before the other tabs, pinned or home, as part of the normal start up procedure, but never closed, but it appears to the right of my home page tab, not the left. I would attempt to visit a website on this ghost tab to get it unstuck, but even clicking on it isn't working. As I recall, it is selected at startup, so I may be able to try that again the next time it happens. That isn't a guaranty, though, and there is also the possibility that Firefox will simply crash when I attempt to visit a webpage, as it appears to be improperly closed.

Occasionally, a new tab will open when starting Firefox in Windows 7 or Ubuntu 12.10. This opens to the default new tab page for Firefox, which I have set to about:blank. This tab cannot be closed by left clicking the "x", by right clicking and selecting close tab from the context menu, or with "Ctrl+W". Additionally, switching between tabs with "Ctrl+Tab" and "Ctrl+Shift+Tab" skips over this tab. It behaves as if it is already closed, but improperly. I suspect it MAY be because it was loaded before the other tabs, pinned or home, as part of the normal start up procedure, but never closed, but it appears to the right of my home page tab, not the left. I would attempt to visit a website on this ghost tab to get it unstuck, but even clicking on it isn't working. As I recall, it is selected at startup, so I may be able to try that again the next time it happens. That isn't a guaranty, though, and there is also the possibility that Firefox will simply crash when I attempt to visit a webpage, as it appears to be improperly closed.

Chosen solution

I haven't seen this bug in a while, I'm going to call it solved. My guess is it was an addon, and the developer caught on and fixed the bug in time for their latest version. I see that some of my addons haven't updated since I posted this bug report (some of them in the last year), so if I see the bug again, I'll just manually update addons on another machine until I can reproduce it. Then I'll tell the developer and post it here, if anyone's interested.

Read this answer in context 👍 1

All Replies (5)

more options

hello, maybe one of your addons is interfering here - however when the issue can't be reproduced reliably then it might be quite difficult to troubleshoot it...

Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems

more options

Inconsistent problems are hard. When extensions update, they sometimes open a new tab to inform you about changes. I wonder whether that is somehow failing halfway through the process?

more options

I do have quite a few addons, I wouldn't be surprised if one of them is opening a new tab unsuccessfully. Is there a way to stop addons from opening tabs after an update? I would imagine that would be built into the addon, meaning "no". Of course, I can't check which addon isn't updating unless it updates, and the next update for the addon could fix this bug entirely. Although, if I could downgrade my addons, I might be able to figure out which developer to contact.

more options

Another idea: I'll disable automatic updates for addons on my desktop for now. When my laptop next sees this bug, I'll backup the profile on the desktop, and update addons one by one. If I don't see this bug again in the next month, I'll call it fixed. (I see the bug every week or so, not really timing it.)

more options

Chosen Solution

I haven't seen this bug in a while, I'm going to call it solved. My guess is it was an addon, and the developer caught on and fixed the bug in time for their latest version. I see that some of my addons haven't updated since I posted this bug report (some of them in the last year), so if I see the bug again, I'll just manually update addons on another machine until I can reproduce it. Then I'll tell the developer and post it here, if anyone's interested.