/?status=deleted filter crashes browsers

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:

This bug does not happen with /?status=unlisted .

1 Like

FWIW It works fine here on meta.

Are there any errors in your /logs?

1 Like

Hmm, nope, nothing corresponding with the time that I try to access /?status=deleted .

1 Like

I wonder if it’s a particular deleted topic that’s the issue. Did you have any notable deletions recently that would stand out?

You could possibly use a data explorer query to review them?

1 Like

Nothing that I can remember. Is the Replies count of -1 possibly an issue?

1 Like

No, it shouldn’t be. I’ve seen a few of those, and had no issue like this before.

I should mention safe mode and errors in the console too, just to be thorough.

1 Like

Thanks, I forgot about safe mode. How do I combine that with ?status=deleted ?

I think you can pop this on the end of your URL - /?status=deleted&safe_mode=no_themes,no_plugins

1 Like

Thanks! So that does avoid the bug. I’ll have to go through all my customizations to figure out which one is causing the problem.

1 Like

Just in case it’s helpful to narrow it down, the appended bits for the 3 flavours of safe mode are:





Ah yes, good call. Thanks again!


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.