High-Signal GitHub & GitLab Bug Report Issue Template

---
name: "Bug Report"
about: "Create a detailed report to help engineering reproduce and fix a bug"
title: "[BUG]: "
labels: ["bug", "triage-needed"]
assignees: ""
---

## 🐛 Bug Description
A clear and concise description of what the bug is.

---

## 🔁 Steps to Reproduce
Steps to reproduce the behavior:
1. Navigate to `/tools/compress-pdf`
2. Select and upload a 15MB PDF containing scanned images
3. Adjust compression slider to `Medium Quality (75%)`
4. Click `Compress Document`
5. Observe that the progress indicator freezes at 84% without throwing an alert

---

## 🎯 Expected Behavior
The compression process should finish, calculate the saved byte ratio, and trigger the browser download prompt with the output PDF.

---

## 💥 Actual Behavior & Error Output
The UI becomes unresponsive for 12 seconds, the progress bar halts, and the console records an unhandled memory exception.

```bash
# Browser Console Stack Trace
Uncaught RangeError: Array buffer allocation failed at PDFWriter.build (pdf-lib.esm.js:1420)
  at async handleCompress (CompressorWorker.ts:88)
  at async HTMLButtonElement.dispatch (bundle.js:412)
```

---

## 🖥️ Environment & System Information
- **DocSwift Version / Commit Hash:** `v2.4.1` (`a8c1f9b`)
- **Operating System:** macOS Sonoma 14.5 (Apple Silicon M2)
- **Browser:** Google Chrome Version 128.0.6613.120 (Official Build) (arm64)
- **Device:** Desktop (Retina 4K Display)
- **File Type / Size Tested:** Scanned Contract PDF (14.8 MB, 32 pages)

---

## 📸 Screenshots or Video Captures
<!-- If applicable, paste a link or drag-and-drop screenshots here -->

---

## 🔍 Additional Context
- Issue does not reproduce on Safari 17.4 or Firefox 129.
- Memory snapshot shows JS heap usage spiking from 45MB to 820MB during the canvas rasterization step.