I have written about it before, one of my longest bug hunts took over 2 weeks. En eventual fix was switching 2 lines of code.
Sure, it was not in our code base, but a somewhat minor bug in a 3rd party library. Which combined with an other 3rd party library, and another one, and the way our code base was set up... it basically made our software unusable.
There was an other bug, which I have no idea how much time I spend in debugging. This again was caused by a combination of 3rd party libraries in a given setup. In total I might have spend way more than 2 weeks to figure this one out. The main issue was that it was leaking memory quite slowly. It took more than a week before you would even notice it in monitoring. It eventually lead to attacking the bug in two libraries [1][2]. I don't know how much time I spend on this as I tried to tackle it multiple times over a long period. It wasn't a really high priority issue.
And then there was a bug which plagued our software for a really long time and resulted in quite some P1 issues where we had to restart the server. This was years ago. It was caused by the bad way our software was set up with mixed technology, resulting in deadlocks which killed the whole system. At that point we were both using our own ORM and Hibernate, mixed with EJBs and other things in Spring. We were kind of in the middle of the transition from JEE and own ORM to a Spring based setup with Hibernate. Some entities were used in both ways. Fixing this was no trivial task. But eventually I figured out a workaround that could sustain us while we (slacked) in continuing the move to the newer technology. Again no idea how much time I spend on this. I also did not really fix the bug.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have written about it before, one of my longest bug hunts took over 2 weeks. En eventual fix was switching 2 lines of code.
Sure, it was not in our code base, but a somewhat minor bug in a 3rd party library. Which combined with an other 3rd party library, and another one, and the way our code base was set up... it basically made our software unusable.
There was an other bug, which I have no idea how much time I spend in debugging. This again was caused by a combination of 3rd party libraries in a given setup. In total I might have spend way more than 2 weeks to figure this one out. The main issue was that it was leaking memory quite slowly. It took more than a week before you would even notice it in monitoring. It eventually lead to attacking the bug in two libraries [1] [2]. I don't know how much time I spend on this as I tried to tackle it multiple times over a long period. It wasn't a really high priority issue.
And then there was a bug which plagued our software for a really long time and resulted in quite some P1 issues where we had to restart the server. This was years ago. It was caused by the bad way our software was set up with mixed technology, resulting in deadlocks which killed the whole system. At that point we were both using our own ORM and Hibernate, mixed with EJBs and other things in Spring. We were kind of in the middle of the transition from JEE and own ORM to a Spring based setup with Hibernate. Some entities were used in both ways. Fixing this was no trivial task. But eventually I figured out a workaround that could sustain us while we (slacked) in continuing the move to the newer technology. Again no idea how much time I spend on this. I also did not really fix the bug.