Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

Mozilla 도움말 검색

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

자세히 살펴보기

65.0.1 crashing on startup

  • 3 답장
  • 1 이 문제를 만남
  • 10 보기
  • 최종 답변자: philipp

more options

Hello.

We have about a half dozen users (some Win7, some Win10 clean images) that are experiencing crashes on startup. If we rename/delete their profile in AppData the crash goes away for a while.

What is ODD is that the crash reports say version 62 and point to two bugs that have been fixed in subsequent versions but we are almost positive the users are on the latest 65.0.1.

Is this just reporting version 62 incorrectly or is there something else we can try? Thanks so much.

https://crash-stats.mozilla.com/report/index/04180a8a-0fac-4d6e-8ea4-e216a0190220#tab-details

Hello. We have about a half dozen users (some Win7, some Win10 clean images) that are experiencing crashes on startup. If we rename/delete their profile in AppData the crash goes away for a while. What is ODD is that the crash reports say version 62 and point to two bugs that have been fixed in subsequent versions but we are almost positive the users are on the latest 65.0.1. Is this just reporting version 62 incorrectly or is there something else we can try? Thanks so much. https://crash-stats.mozilla.com/report/index/04180a8a-0fac-4d6e-8ea4-e216a0190220#tab-details

모든 댓글 (3)

more options

hello, all metadata in the crash reports point towards firefox 62 really having been in use while the crash was taking place, so you should look into that matter... the crashing problem arises when older versions of firefox access a profile that got modified by firefox 64 or later.

more options

Thanks for your reply.

Yes, that is what we are thinking too, the crash is coming from 62.

We have some machines that have 65.0.1 Firefox installed but an older version of Mozilla Maintenance Service at 62. We ran the maintenance installer which is in the FireFox directory and it silently upgraded to 65.0.1.

Could that have been causing this? Should that Maintenance service autoupdate?

more options

no, i don't think the older mozilla maintenance service would cause it - afaik it's functionality hasn't changed in ages and the version number in the system control panel is just declarative.

could you check if users perhaps have a mozilla firefox program folder containing firefox.exe somewhere within their user path? this might happen if users without admin rights are trying to run the firefox installer - then they might end up with one version that's installed in c:\program files\ and another one within c:\users....