Closed Bug 1356790 Opened 9 years ago Closed 9 years ago

Firefox reliably crashes on this website

Categories

(Firefox :: Untriaged, defect)

52 Branch
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: bugzillamozilla, Unassigned)

Details

(Keywords: crash, stackwanted)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20170329150849 Steps to reproduce: Visit website http://downdetector.co.uk/problems/talktalk/map/ I am using Firefox 52.0.2 (64-bit) Firefox for Ubuntu canonical - 1.0 Actual results: Browser crashes immediately Expected results: Browser should not crash
please attach some crash report ids from about:crashes
Severity: normal → critical
Keywords: crash, stackwanted
I'm wondering about privacy implications of sending crash report. Is there a web page somewhere that explains exactly what information gets sent in such reports (e.g., browsing history, cookies, passwords, ...)?
(In reply to Alex from comment #2) > I'm wondering about privacy implications of sending crash report. Is there a > web page somewhere that explains exactly what information gets sent in such > reports (e.g., browsing history, cookies, passwords, ...)? There is no history, password and other privacy information is uploaded. Your environment information will be uploaded, including your add-on meta information. https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Crash_reporting
I navigated to http://downdetector.co.uk/problems/talktalk/map/ in Firefox 52.0.2 (64-bit) for canonical-1.0 (as reported) multiple times and it did not crash the browser. My install, however, is clean (i.e. no add-ons). I would suggest further investigation into possible add-on related issues as the browser does not seem to be the direct cause of the crash.
Now that webpage works for me too without crashing. Possibly something changed at the website end, or possibly the difference is that I have since rebooted my computer, so I may be running a slightly different kernel or graphics card driver or other software as a consequence of any updates that happened since the previous reboot. So it looks like this won't be debugable since we can't reproduce it, unless someone else can reproduce it. I'm sorry I didn't upload the crash report at the point it was reliably crashing. To tell the truth, I wasn't reassured by YF's statement about privacy information. I followed the suggested link, https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Crash_reporting, but that did not appear to give any guarantees about what was and was not uploaded. In fact it confirmed that because some uploaded information was personal/private, it is only accessible to Mozilla developers. Next time I'll replicate the issue on a live install and submit a crash report from a clean computer that way.
Hello Alex, I am closing this bug for now as issue is not reproducible for you. In case you encounter the crash again please reopen this bug and provide the crash ID. Thanks!
OK, I'll probably do that next time. However, I would suggest that it is clearly spelled out somewhere exactly what information is contained in a crash report, and who has access to which parts of it. (I still haven't found anywhere that explains this.) At the moment it is hard to form a judgement as to what privacy issues there are or aren't in submitting such a report.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.