Worse still for Mozilla, it can’t now tell which crash dump data was collected on account of the bug, and which of it was collected with consent. That’s why some users (we’re amongst that number) err on the side of caution and deliberately turn off crash reporting, for all that it might benefit the community to have it enabled.Īnd therein lies a dilemma for Mozilla: the organisation may already have collected data that wasn’t supposed to be uploaded, something that this update can’t reach back in time and fix. ![]() With low frequency they may contain private or identifying information. ![]() However, as Mozilla notes, there is a small risk of personal data escaping in a crash report, not least because the information uploaded comes from the memory space of a program that has already misbehaved by crashing in the first place:Į need to be mindful that crash dumps contain the contents of the crashing tab. You can check your own settings on the about:preferences#privacy page, in the section about data collection: As bugs go, this one doesn’t sound terribly serious – not least because many users have Mozilla’s crash reporting turned on anyway, as a way of helping the development team.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |