It's very common in gaming circles (not game dev afaik, just ppl who play games). I found it weird wording too, at first; it seemed like a euphemism for 'bug' to me, but I think I now have a more nuanced understanding. I think a 'glitch' (to people outside the software industry) is something that makes software behave in strange or 'wrong', unintended ways, but not crash or give straight up gibberish results. Like, a game crashing is a 'bug' but a character being transported across the map is a 'glitch'.

Likewise, if software rounds bank transfers to the nearest thousand $ and loses the remainder, but only on Thursdays when there is an 'r' in the month, then that's a glitch; but when the software doesn't open that's a 'bug' (or rather, 'it doesn't work').

It's an inconsequential difference from a software engineering pov, but in my experience it's major to outsiders, to the point where they start looking for workarounds for 'glitches' or explain things away, but throw their hands up at the first sign of a 'doesn't work'. I don't understand the thinking, but at least trying to understand users in similar circumstances has made me realize that there are things where I just can't understand someone else's point of view, in which case I need to switch problem solving or design methods; because no matter how hard I try, my 'how is that not obvious' approach isn't going to work.