Crash Reports in Oasis for Desktop

Crash Metadata

Basic information about the crash environment:

• Operating System: Windows, macOS, Linux version and details
• Firefox Version: Exact browser version that crashed
• Crash Timestamp: When the crash occurred
• Platform Information: Hardware architecture and system details

Device Memory Usage

Memory information at crash time:

• Available Memory: How much RAM was free when crash occurred
• Memory Pressure: Whether system was under memory stress
• Memory Allocation: How Firefox was using system memory
• Low Memory Detection: Helps identify memory-related crashes

Crash Stack Traces

Technical details about the crash:

• Code Execution Path: What Firefox was doing when it crashed
• Function Calls: Sequence of function calls leading to crash
• Error Identification: Specific error codes and messages
Third-party Code: Whether crash was in Firefox or external code

Memory Snapshots

Small fragments of program memory:

• Crash Context: Memory state at crash moment
• Variable Values: Important data that might explain the crash
Private Information: May contain sensitive data (limited access)
• Developer Access: Only accessible by small number of Mozilla engineers

Browsing Metadata

Optional information about browsing activity:

• Current URL: Page loaded when crash occurred (opt-in)
Tab Information: Which tabs were open and active
• Page Content: Basic page structure information
• Reproduction Context: Helps developers reproduce the crash

Hardware Testing Results

System hardware diagnostics:

• Hardware Validation: Simple tests to identify bad hardware
Performance Metrics: System performance indicators
• No Personal Data: Results don't contain identifiable information
• User Control: Users can opt-out of hardware testing

Crash Ping vs. Crash Report

Understanding the difference:

• Crash Pings: Smaller, automatic reports with minimal data
• Crash Reports: Detailed reports with comprehensive crash information
Automatic vs. Manual: Pings are automatic, reports are user-controlled
• Data Volume: Pings contain much less information than full reports

Crash Ping Content

What crash pings include:

• Non-identifying Metadata: Basic crash information without personal data
Crash Frequency: How often crashes occur
• Platform Statistics: Crash patterns across different systems
Background Process Crashes: Crashes in background browser processes

Benefits of Crash Pings

Why crash pings are valuable:

• Better Bug Prioritization: More accurate crash impact assessment
Background Process Insights: Information about crashes not captured in reports
• Stability Metrics: Overall browser stability measurement
Trend Analysis: Long-term crash pattern identification

Desktop Settings Configuration

To enable automatic crash report submission:

1. In the Menu bar at the top of the screen, click Firefox and select Settings (select Preferences on older macOS versions)
2. Click the menu button and select Settings
3. Go to the Privacy & Security panel
4. Scroll down to the Firefox Data Collection and Use section
5. Check or uncheck the box next to Automatically send crash reports

Note: In Oasis, the menu structure may vary slightly, but the setting should be located in the Privacy & Security section under Firefox Data Collection and Use.

Setting Options

What each setting means:

• Enabled (Checked): Firefox automatically sends crash reports
Disabled (Unchecked): Default setting - crash reports saved locally
• Manual Control: You choose when to send each report
Immediate Submission: Reports sent as soon as crashes occur

Automatic Submission Benefits

When automatic crash reports are enabled:

• Immediate Data: Mozilla receives crash data right away
Faster Bug Fixes: Developers can start working on fixes immediately
• Better Prioritization: More accurate crash impact assessment
Improved Stability: Faster resolution of stability issues

Default Behavior (Disabled)

When the option is disabled:

• Local Storage: Crash reports saved on your device
Manual Control: You decide when and which reports to send
• Prompt After Crash: Firefox asks if you want to send report
Delayed Analysis: Mozilla doesn't receive crash data immediately

User Choice

Maintaining control over your data:

• Opt-in Approach: You choose whether to participate
Transparency: Clear information about what data is sent
• Privacy Control: Maintain control over your information
Contribution Choice: Decide how to help improve Firefox

Immediate Submission

After a crash occurs:

• Crash Prompt: Firefox asks if you want to send crash report
Quick Decision: Choose to send or not send immediately
• No Delay: Report sent right away if you choose to send
User Control: You maintain control over each submission

Delayed Submission

Submit reports later:

• Access Crash History: Navigate to about:crashes in URL bar
Review Reports: See all saved crash reports on your device
• Selective Submission: Choose which reports to send
Batch Processing: Send multiple reports at once

About:Crashes Page

Managing your crash reports:

• Complete History: View all crashes that occurred
Report Details: See what information each report contains
• Submission Control: Choose which reports to send to Mozilla
Local Management: Organize and review crash data

Data Minimization

Mozilla's approach to crash data:

• Limited Access: Only small number of engineers can access reports
Anonymous Processing: Personal information is minimized
• Purpose Limitation: Data used only for crash analysis
Secure Transmission: Reports encrypted when sent to Mozilla

User Control

How you maintain privacy:

• Opt-in Choice: You decide whether to send reports
Manual Review: Review reports before sending
• Selective Submission: Choose which crashes to report
Complete Opt-out: Disable all crash reporting if desired

Data Handling

How Mozilla protects your data:

• Limited Retention: Crash data not stored indefinitely
Secure Storage: Data stored in secure, controlled environments
• Access Control: Strict controls on who can access reports
Regular Review: Data practices regularly reviewed and updated

When to Enable Automatic Reports

Consider enabling automatic submission if:

• Stability Focus: You want to help improve browser stability
Frequent Crashes: You experience crashes regularlyDevelopment Support: You want to contribute to Firefox developmentPrivacy Comfort: You're comfortable with the data being sent

When to Use Manual Control

Consider manual control if:

• Privacy Concerns: You prefer to review data before sending
Infrequent Crashes: You rarely experience browser crashesSelective Reporting: You want to choose which crashes to reportNetwork Limitations: You have limited internet connectivity

Balancing Privacy and Contribution

Finding the right balance:

• Understand the Data: Know what information is being sent
Assess Benefits: Consider how your data helps improve Firefox
• Review Regularly: Periodically review your crash reporting settings
Stay Informed: Keep up with Mozilla's privacy practices

Reports Not Sending

If crash reports aren't being sent:

• Check Settings: Verify automatic submission is enabled
Network Issues: Ensure stable internet connection
• Firewall Settings: Check if firewall is blocking submissions
Privacy Extensions: Disable conflicting privacy extensions

Accessing Crash History

If you can't access about:crashes:

• Type Correctly: Ensure you type about:crashes exactly
Check Permissions: Verify browser has permission to access local data
• Clear Cache: Clear browser cache and cookies
Restart Browser: Restart Oasis to refresh crash data

Privacy Concerns

If you're concerned about data privacy:

• Review Settings: Check all data collection settings
Read Privacy Notice: Understand Mozilla's data practices
• Contact Support: Reach out to Mozilla support with questions
Opt Out Completely: Disable all data collection if needed