It depends. Some other reasons:
1. It's an enterprise product and the economic buyer doesn't know or care about bugs as much as checklisted features.
2. The company is not connecting the impact of fixing bugs to their bottom line. Or they are and estimate the impact to be low.
3. The code base is due for a rewrite so it would be a waste.
4. It's a side bet not worth the extra resources.
We make a niche B2B software for a low-margin sector. For us it's definitely point 1.
We of course fix the serious issues, but we also leave a lot of bugs collecting virtual dust in our tracker.
While I know our customers get annoyed with bugs, they care a lot more about essential features and low price.
Now, we're in the process of incrementally rewriting our 20+ year old software, and code quality has a very high priority now. So hopefully the future will be brighter.
That said, our users are incredibly good at finding weird issues.