Depends on the bug. A major performance and cache corruption bug in production had four people (on a 6 person team) each spending probably 12 hours per week on

Depends on the bug. A major performance and cache corruption bug in production had four people (on a 6 person team) each spending probably 12 hours per week on it for two months. A complex corner case that gets hit twice per week out of 100 million requests has been ignored for two years. A bug that only affected bad actors (people hitting a spam detection threshold, even in good faith, were getting 500 errors instead of a warning) waited a week even though it was just an obvious one-line fix. The thing about bugs is that you often don't know what's causing them, and some are too complex or require too-specific conditions to be able to track down. If you don't know what's causing it, there's no way to know how difficult it will be to fix. So most bugs get - if not timeboxed - heavy follow up and pressure to fix it or drop it or work around it after a couple days of non-progress. But there are some bugs you just have to keep working on until you squash them, no matter how long that takes.