We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Firefox closes the wrong tab while closing multiple pages.

  • 4 답장
  • 1 이 문제를 만남
  • 1 보기
  • 최종 답변자: MightyMoe

more options

It's really tricky to describe... Ok, let's say i want to search firefox logo via google images. I found a lot of interesting results and opened them in different tabs. Now i found one pic that i really like and want to close tabs i dont need anymore. I'm not changing active tab and just pressing crosses to close desired inactive tabs. I care for my time and automatically doing it fast. But after 2 tabs closed, third tab not only closes itself, but it makes my active tab close too!

This happens no matter what pages i use, how many are open, memory usage, etc. It just happens no matter what. There are only 2 conditions i need to meet: - Close tabs that are inactive - Do it fast

I'd really appreciate some help with my problem because the tab that usually accidentally crash is the tab with a lot of edited text. You can imagine how disappointing it may be.

Thank you.

It's really tricky to describe... Ok, let's say i want to search firefox logo via google images. I found a lot of interesting results and opened them in different tabs. Now i found one pic that i really like and want to close tabs i dont need anymore. I'm not changing active tab and just pressing crosses to close desired inactive tabs. I care for my time and automatically doing it fast. But after 2 tabs closed, third tab not only closes itself, but it makes my active tab close too! This happens no matter what pages i use, how many are open, memory usage, etc. It just happens no matter what. There are only 2 conditions i need to meet: - Close tabs that are inactive - Do it fast I'd really appreciate some help with my problem because the tab that usually accidentally crash is the tab with a lot of edited text. You can imagine how disappointing it may be. Thank you.

선택된 해결법

Thx you all guys!

The support of Easy App Tabs 5 is faster than i thought and looks like problem is solved for now. Bugfix should be added to the next update, but if you don't want to wait (as i do), you can grab the solution from here.

Best luck.

문맥에 따라 이 답변을 읽어주세요 👍 0

모든 댓글 (4)

more options

Hello,

Try Firefox Safe Mode to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.

(If you're not using it, switch to the Default theme.)

  • You can open Firefox 4.0+ in Safe Mode by holding the Shift key when you open the Firefox desktop or Start menu shortcut.
  • Or open the Help menu and click on the Restart with Add-ons Disabled... menu item while Firefox is running.

Once you get the pop-up, just select "'Start in Safe Mode"

If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, and you need to figure out which one. Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article for that.

To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.

When you figure out what's causing your issues, please let us know. It might help other users who have the same problem.

Thank you.

more options

Thx, colbabomb. Figured out it was Easy App Tabs 5 doing damage.

What should i do now? Can anybody suggest another addon for pinning tabs by doubleclicking or maybe fix this issue in existing addon?

more options

Report that issue to the developer of that add-on.
https://github.com/supahgreg/easy-app-tabs/issues

more options

선택된 해결법

Thx you all guys!

The support of Easy App Tabs 5 is faster than i thought and looks like problem is solved for now. Bugfix should be added to the next update, but if you don't want to wait (as i do), you can grab the solution from here.

Best luck.