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!

Mozilla 도움말 검색

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

자세히 살펴보기

Firefox fails to unload after closure

  • 7 답장
  • 45 이 문제를 만남
  • 3 보기
  • 최종 답변자: John99

more options

I am a veteran Firefox user ( internet user since 1990) & have upgraded to FF 29.0 but ever since upgrading the outstanding problem is almost every time I load a browser session. Once I have finished and close the browser. It seems FF doesnt actually unload FF from memory, so that the next time I attempt to open FF it fails to load and reports the previous session remains open. i.e. is still using memory & has a service/process open. Thus it appears FF fails to actually close one session & unload itself from memory so that a fresh session cannot be initiated. I have to terminate FF with windows task manager before I can re-open a new session. Please can you suggest a solution for this problem. PS: Firefox is working perfectly on my machine apart from this problem.

DELL Vostro 22os computer, OS= windows 7 pro 32bit with SP1, 4 GB memory, AMD 4300/4500 graphics adapter. Ethernet connection to the web over ADSL2 service.

I am a veteran Firefox user ( internet user since 1990) & have upgraded to FF 29.0 but ever since upgrading the outstanding problem is almost every time I load a browser session. Once I have finished and close the browser. It seems FF doesnt actually unload FF from memory, so that the next time I attempt to open FF it fails to load and reports the previous session remains open. i.e. is still using memory & has a service/process open. Thus it appears FF fails to actually close one session & unload itself from memory so that a fresh session cannot be initiated. I have to terminate FF with windows task manager before I can re-open a new session. Please can you suggest a solution for this problem. PS: Firefox is working perfectly on my machine apart from this problem. DELL Vostro 22os computer, OS= windows 7 pro 32bit with SP1, 4 GB memory, AMD 4300/4500 graphics adapter. Ethernet connection to the web over ADSL2 service.

선택된 해결법

hello Cyteck, a wild guess: could you try entering "about:config" into the address bar, searching for the preference "network.seer.enabled" and setting it to "false" for testing purposes? thank you...

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

모든 댓글 (7)

more options

선택된 해결법

hello Cyteck, a wild guess: could you try entering "about:config" into the address bar, searching for the preference "network.seer.enabled" and setting it to "false" for testing purposes? thank you...

more options

THANKS very much this does indeed apear to have resolved this matter as far as I can see. I have tested FF openning & closing it. It does indeed unload smaoothly now. THANKS Again much appreciated too.

Kind Regards Ivan

more options

I made this change [it's still set to false] and it seemed to work one time only. But I'm right back to using Task Manager to kill FF29 before I can open a new window. HELP! or give me a "roll back" option to v28

more options

At least for me, it seems to be more of an issue on my 64 bit Win 7 machine. My 32 bit Win 7 doesn't seem to act up this way. and yes, network.seer.enabled is still set to false and I continue to have to use Task Manager to kill FF29 before I can open another session.

more options

Wow, mine was already set to "false" so changed it to "true" and, fingers crossed, it seems to be working on both computers.

more options

Was wishful thinking. Playing up again and it is starting to really annoy me! Not interested in Chrome because I have to sign in to Google and I don't see why. IE is out of the question so it may be a Linux Mint solution for me.

more options

UPDATE

This relates to those cases where the problem continues in Firefox 29.0.1 if History is set to be cleared on close down.


Note one potential fix is now in the very recent Firefox Beta 30b8 Initial reports suggest this fixes the issue. (Bug1005487#c38) If you have been suffering from this problem and want a fix now instead of in a few weeks time you may wish to download and install the Beta version of Firefox.

The beta version is effectively a release candidate but is only intended for advanced users or testers. I would be interested to hear feedback from those of you that do test this out.

Beta version download