Searching and Filing Bugs on the Chromium Issue Tracker

This article provides a straightforward guide on how to use the public Chromium Issue Tracker to find existing bugs and submit new reports. By learning how to effectively search the database and properly format a bug submission, users can directly assist developers in identifying, reproducing, and resolving issues within the Chromium web browser.

Accessing the Tracker

To begin, navigate to the Chromium Issue Tracker at issues.chromium.org. While anyone can search and view public bugs, you must sign in with a Google account to file a new report, star existing issues, or leave comments.

How to Search for Existing Bugs

Before filing a new bug report, you must search the tracker to ensure the issue has not already been reported. Submitting duplicate reports slows down the development process.

  1. Use the Search Bar: Locate the search bar at the top of the page. Enter specific keywords related to the problem, such as exact error messages, the affected web API, or the specific browser feature (e.g., "WebRTC audio drop" or "bookmark bar crash").
  2. Apply Filters: By default, the tracker searches open issues. You can refine your search by clicking the filter icon or typing search operators. Useful filters include operating system (OS), component, and status (e.g., Open, Fixed, Verified).
  3. Review the Results: Scan the titles of the returned issues. Click on relevant entries to read the description and confirm if the reproduction steps match your experience.
  4. Star the Issue: If you find an existing report that matches your bug, do not post a comment just to say "me too." Instead, click the star icon next to the issue title. Starring the bug notifies developers of how many people are affected and subscribes you to email updates regarding its progress. Only leave a comment if you can provide new, relevant technical data.

Preparing to File a Bug

If your search yields no results, you should file a new report. Gather the following information from your browser before starting:

  • Version and OS Data: Open a new tab, type chrome://version into the address bar, and press Enter. Keep this page open, as you will need to copy this data into your report.
  • Crash IDs (if applicable): If the bug involves a browser crash, navigate to chrome://crashes. Copy the "Uploaded Crash Report ID" associated with the event.
  • Clean Profile Test: Verify that the bug is not caused by a third-party extension. Open an Incognito window (with extensions disabled) or create a new, clean user profile and try to trigger the bug again.

How to File a New Bug Report

Once you have verified the bug is unique and gathered your system data, follow these steps to submit the report:

  1. Initiate the Report: Click the Create Issue button located in the top-left corner of the Issue Tracker interface.
  2. Select the Correct Template: Choose the appropriate category from the template dropdown menu. Most regular browser malfunctions fall under "Defect report from user." If you are reporting a vulnerability, select the "Security" template to ensure the report remains restricted from public view until patched.
  3. Write a Clear Title: In the Summary field, write a brief, specific title that summarizes the exact problem (e.g., "Clicking print button on PDF files crashes the tab on macOS").
  4. Fill Out the Description: The template will provide prompts inside the description box. Fill them out directly:
    • Browser Version: Paste the information from your chrome://version page.
    • Steps to Reproduce: Write a numbered list of the exact, minimal steps required to trigger the bug. Include a specific URL if the bug only happens on a certain website.
    • Expected Result: State clearly what the browser should do if it were working correctly.
    • Actual Result: State what actually happens instead.
  5. Attach Supporting Files: Use the attachment button at the bottom of the form to upload screenshots, screen recordings, minimal HTML test cases, or system logs that help demonstrate the issue.
  6. Submit: Click the Create button at the bottom of the page to publish your report.

Following Up on Your Report

After submission, your bug will be triaged by the Chromium team. Monitor the email associated with your Google account for notifications. Developers may leave comments on your issue asking for further clarification, specific log files, or asking you to test a fix in Chromium Canary (the daily developer build). Responding promptly to these requests ensures your bug has the highest chance of being resolved.