Oops, just realized that we forgot to request data-review. Here we go. # What questions will you answer with this data? Attempting to detect which crashes are related to low-memory on macOS. # Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements? Some example responses: Because we want to fix crashes. # List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the Mozilla wiki. - Available physical memory at the time of crash (Technical data) - Available swap memory at the time of crash (Technical data) - Purgeable physical memory at the time of crash (Technical data) - Total physical memory (Technical data) # How long will this data be collected? Choose one of the following: Forever, as part of crash monitoring. # What populations will you measure? All macOS users (note that Windows users are already measured) # Which release channels? All # Which countries? All # Which locales? All # If this data collection is default on, what is the opt-out mechanism for users? Part of crash signatures. We don't change the mechanism for opting in/out. # Please provide a general description of how you will analyze this data. Correlating crashes with memory conditions. # Where do you intend to share the results of your analysis? As part of the comments and/or tests of Firefox patches fixing crashes. # Is there a third-party tool (i.e. not Telemetry) that you are proposing to use for this data collection? Nope, this uses the crash monitor.
Bug 1587721 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Oops, just realized that we forgot to request data-review. Here we go. ## What questions will you answer with this data? Attempting to detect which crashes are related to low-memory on macOS. ## Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements? Some example responses: Because we want to fix crashes and ship Fission. ## List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the Mozilla wiki. - Available physical memory at the time of crash (Technical data) - Available swap memory at the time of crash (Technical data) - Purgeable physical memory at the time of crash (Technical data) - Total physical memory (Technical data) ## How long will this data be collected? Choose one of the following: Forever, as part of crash monitoring. ## What populations will you measure? All macOS users (note that Windows users are already measured) ## Which release channels? All ## Which countries? All ## Which locales? All ## If this data collection is default on, what is the opt-out mechanism for users? Part of crash signatures. We don't change the mechanism for opting in/out. ## Please provide a general description of how you will analyze this data. Correlating crashes with memory conditions. ## Where do you intend to share the results of your analysis? As part of the comments and/or tests of Firefox patches fixing crashes. ## Is there a third-party tool (i.e. not Telemetry) that you are proposing to use for this data collection? Nope, this uses the crash monitor.