Maybe the fix didn't work for all users but was a workaround for some of them. A few users in bug 1181091 (and an user in bug 1294650) mention that storing a shim QIPCAP.dll file in the Firefox installation directory fixed the issue for them. Should we keep the dll shim as a mitigation, even if it doesn't fix the issue for all users? The last times we had similar issues with WebSense (bug 828184 and bug 1181091) we weren't able to do anything but had to wait for a new WebSense release.

👁 Image	Marco Castelluccio [:marco]
	Comment 3 • 9 years ago

It doesn't make sense to keep the workaround anymore, since WebSense has fixed the issue and we have a hotfix to prevent people using WebSense from updating.

👁 Image	Liz Henry (:lizzard)
	Comment 4 • 9 years ago

Jimm, Marco just pointed this out to me. Are you doing the backouts? Should someone else do it? Thanks.

👁 Image	Jim Mathies [:jimm] Reporter
	Comment 5 • 9 years ago

we don't want to keep this dummy dll in our install. For backouts, tree managers can handle backing out the appropriate cset on each tree itemized in the first comment.

Keywords: checkin-needed

👁 Image	u194118
	Comment 6 • 9 years ago

(In reply to Marco Castelluccio [:marco] from comment #3) > It doesn't make sense to keep the workaround anymore, since WebSense has > fixed the issue and we have a hotfix to prevent people using WebSense from > updating. well, I still have the old websense version on my professionnal computer, I've already updated to FF 48.0.2 and the workaround works for me... Without a websense update on my computer and with the workaround backout, FF will crash again on my computer with the next version..

👁 Image	Liz Henry (:lizzard)
	Comment 7 • 9 years ago

Wes, can you back out the patches in comment 0 so we will have the dummy dll removed for the 49 release candidate build? Thanks.

Flags: needinfo?(wkocher)

👁 Image	Marco Castelluccio [:marco]
	Comment 8 • 9 years ago

(In reply to jcleval from comment #6) > well, I still have the old websense version on my professionnal computer, > I've already updated to FF 48.0.2 and the workaround works for me... Without > a websense update on my computer and with the workaround backout, FF will > crash again on my computer with the next version.. You can update WebSense to avoid the crash (they have found the cause and fixed it). If you aren't able to update before Firefox 49 is released (but you have some time), you can create a dummy DLL yourself (or just copy the current one from the Firefox folder and copy it back after the update).