User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171206182557 Steps to reproduce: General web browsing with the following extensions installed: LastPass OneNote Web Clipper Cisco WebEx WebRoot Filtering Extension Actual results: Firefox became unresponsive and had to be force quit. The following was recorded in the event log: P1: firefox.exe P2: 18.104.22.16849 P3: 10.0.16222.214.171.124 P4: P5: P6: P7: P8: P9: P10: Attached files: \\?\C:\Users\RYAN~1.DOR\AppData\Local\Temp\RDRF0E1.tmp\empty.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF0F2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF12F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF150.tmp.txt These files may be available here: Analysis symbol: Rechecking for solution: 0 Report Id: 5f0a43e4-abba-485e-908a-eb6d67a7c1d9 Report Status: 268435456 Hashed bucket: 7716f1ebb0de4631fe9182f0996f6796 Expected results: Firefox should have continued to function normally
I tried to get the files referenced in the Event Log entry but they were gone.
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 Firefox: 57.0.2, Build ID 20171206182557 I have not managed to reproduce the issue on Windows 10 x64, Ubuntu 14.04 x64 and Mac 10.12 with Firefox release (57.0.2) and the latest Nightly (59.0a1) build installed. I've installed the following add-ons: LastPass, OneNote Web Clipper; Cisco WebEx; (I could not find the WebRoot Filtering Extension add-on) and I have not encountered any hangs, freezes or crashes. While looking for the WebRoot add-on I've found the following support link https://support.mozilla.org/en-US/questions/1082889, so there is a chance that this issue is caused by it. Could you please retest this issue without the WebRoot add-on installed? If the WebRoot add-on caused this, then probably this issue is related to Bug 1371387. Jim, could you please give us your opinion regarding this issue?
Marking this as Resolved - Incomplete due to the lack of response from the reporter. If anyone can still reproduce it on the latest versions, feel free to reopen the issue and provide more information.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 19 days ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.