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!

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Firefox crashes

  • 2 个回答
  • 3 人有此问题
  • 1 次查看
  • 最后回复者为 erindshaw

more options

Getting Crash ID: bp-700fea1a-48eb-49c5-b4cf-4b61f2160608 when trying to install Firefox 45.2.0 ESR. Deploying thru SCCM but also crashes when installing locally from the .exe. Original install did include a .cfg, .ini, .js and .cmd file. Have used the files to install previous ESR versions with no problems. Uninstalling and reinstalling from just the .exe doesn't fix the problem. Installing previous versions and consumer version doesn't work to fix it either. Still crashing every time it's launched. Crashes in safe mode as well.

Getting Crash ID: bp-700fea1a-48eb-49c5-b4cf-4b61f2160608 when trying to install Firefox 45.2.0 ESR. Deploying thru SCCM but also crashes when installing locally from the .exe. Original install did include a .cfg, .ini, .js and .cmd file. Have used the files to install previous ESR versions with no problems. Uninstalling and reinstalling from just the .exe doesn't fix the problem. Installing previous versions and consumer version doesn't work to fix it either. Still crashing every time it's launched. Crashes in safe mode as well.

被采纳的解决方案

I'm not 100% certain, but the modules list includes a Websense Endpoint DLL (qipcap.dll), so it could be a new incompatibility with that program. Usually the ESR release is well supported by Websense so this is a little mysterious.

A workaround Firefox users sometimes employ is to create a fake qipcap.dll file that will block Firefox from using the incompatible qipcap.dll file. Please see this post for more information on this option, which I have not tried myself: https://support.mozilla.org/questions/1111324#answer-847872

定位到答案原位置 👍 1

所有回复 (2)

more options

选择的解决方案

I'm not 100% certain, but the modules list includes a Websense Endpoint DLL (qipcap.dll), so it could be a new incompatibility with that program. Usually the ESR release is well supported by Websense so this is a little mysterious.

A workaround Firefox users sometimes employ is to create a fake qipcap.dll file that will block Firefox from using the incompatible qipcap.dll file. Please see this post for more information on this option, which I have not tried myself: https://support.mozilla.org/questions/1111324#answer-847872

more options

You rock, J! Thank you so much for the quick reply and solution. I would have never figured THAT out and since I use my director's PC as a test subject for new packages (meaning I blew his FF up too), a quick fix was wonderful!