Any bug is a headache.
On the one hand, bug fixing is expensive in terms of both time and money. It takes resources and time that could be allocated to new feature development, pushing your project back.
On the other hand, not fixing bugs is risky for the development process, business and even for end-users’ lives in some cases. It creates obstacles and technical debt. It makes users unhappy and leads to costly outcomes in fulfilling the business need.
So what is the proper solution? The trick is in fixing the right stuff. You should balance between bug fixing and implementing new requirements by prioritizing your bug fixes properly.