TemplateDocs
Bug report
A bug report template covering environment, exact repro steps, expected vs. actual behavior, severity with justification, and evidence.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your document
# Bug: Export button freezes the page on large reports
**Environment:** Chrome 128 on macOS 14, production, Enterprise plan · **Severity:** P1 - blocks a core workflow
## Steps to reproduce
1. Open a report with more than 5,000 rows
2. Click "Export to CSV"
3. Watch the page instead of a file downloading
## Expected behavior
The CSV downloads within a few seconds and the page stays responsive while it generates.
## Actual behavior
The page freezes completely for 45+ seconds, then the tab crashes with an out-of-memory error. No file downloads.
## Why this severity
Marked P1 because it affects every Enterprise account - our largest reports are all above 5,000 rows - and there is no workaround, since export is the only way to get this data out.
## Evidence
Screen recording: bug-export-freeze.mp4 (attached). Console log shows heap allocation climbing past 1.8GB before the crash.
How to use it well
- →Repro steps only count if a stranger with no context can follow them and hit the bug - if a step relies on knowledge only you have, it isn't a reproduction, it's a memory.
- →Justify the severity in the report itself. "P1" without a sentence explaining who it blocks and whether there's a workaround gets triaged on vibes and re-litigated later.
- →One piece of concrete evidence - a recording, a log line, a stack trace - resolves more severity arguments than three paragraphs of description.