Memory leak and crash

[coreylane]

Running Overseerr version 1.29.1 for two months without issue. Nothing has changed with my configuration or setup at all recently. Suddenly whenever I try to access web UI the app starts consuming memory until it finally exhausts and crashes

The only thing I can think of recently is downloaded several hundred episodes of House Hunters..... could my sql lite db be corrupted? Anyway to repair/integrity check, or just start over? Thanks

today at 12:31:55 AM <--- Last few GCs --->
today at 12:31:55 AM
today at 12:31:55 AM [267:0x14827ad9a330]   139432 ms: Mark-sweep (reduce) 4065.1 (4144.0) -> 4064.2 (4144.0) MB, 1056.5 / 0.0 ms  (average mu = 0.829, current mu = 0.007) allocation failure scavenge might not succeed
today at 12:31:55 AM [267:0x14827ad9a330]   140489 ms: Mark-sweep (reduce) 4065.4 (4144.0) -> 4064.6 (4144.2) MB, 1049.7 / 0.0 ms  (average mu = 0.702, current mu = 0.007) allocation failure scavenge might not succeed
today at 12:31:55 AM
today at 12:31:55 AM
today at 12:31:55 AM <--- JS stacktrace --->
today at 12:31:55 AM
today at 12:31:55 AM FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
today at 12:31:56 AM error Command failed with signal "SIGABRT".
today at 12:31:56 AM info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

1. What version of Overseerr are you running? 1.29.1
2. How did you install Overseerr? hotio / overseerr - This container has been working great for 7 months. No recent updates
3. How are you accessing Overseerr? Have a reverse proxy config setup with "Nginx Proxy Manager" - Crash also occurs when accessing container directly (http://192.168.1.100:5055)
4. Are you accessing Overseerr through your reverse proxy or via a local IP address? Both methods result in crash
5. What browser are you using? What browser extensions are enabled? Tried all browsers and other devices like my phone
6. What were you trying to do, and how did you attempt it? Accessing overseerr homepage causes sudden spike in mem usage