# /?status=deleted filter crashes browsers

**URL:** <https://meta.discourse.org/t/status-deleted-filter-crashes-browsers/277234>\
**Category:** Product Support\
**Created:** [August 30, 2023, 6:11pm UTC](https://meta.discourse.org/t/status-deleted-filter-crashes-browsers/277234 "2023-08-30T18:11:26Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![rahim123](https://avatars.discourse-cdn.com/v4/letter/r/df705f/32.png) [@rahim123](https://meta.discourse.org/u/rahim123)\
**Post date:** [August 30, 2023, 6:11pm UTC](https://meta.discourse.org/t/status-deleted-filter-crashes-browsers/277234/1 "2023-08-30T18:11:26Z")

</div>

Hi there, really weird bug where the `/?status=deleted` filter is rendering an incomplete and frozen page that doesn’t allow for interaction with the UI elements, causing the browser CPU usage to skyrocket, and eventually crashing the process for the browser tab. This is happening with Firefox 102.13 ESR and Chromium 115.0.5790.98, both on Debian 12. Here’s what the page looks like:

 ![Screenshot from 2023-08-30 13-04-46](https://global.discourse-cdn.com/meta/original/4X/5/9/b/59b9b8ef1f1ae75157d9958ba8304976c769a352.png)

This bug does _not_ happen with `/?status=unlisted` .

---

_[View the full topic](https://meta.discourse.org/t/status-deleted-filter-crashes-browsers/277234)._