It's fine to close it if it's been triaged, if there's some actual reason to believe it may no longer apply, such as big changes having happened in the subcomponent with the bug after the filing of the bug.
That's not the behaviour I've been seeing though. Instead what I've seen are mechanical mass-closings of the "This is 9 months old, and we're released a new version, so it's being closed", even in cases where the bug was narrowed down to specific functions that hasn't had a single change in those 9 months.
If they instead put it at "NEED INFO" and didn't get any, in a reasonable amount of time, then okay, fine, close the sucker. But I've never once seen that happen. Instead the bug goes straight from "CONFIRMED" to "CLOSED" with no questions posed.
The routine should be to *either* investigate slightly to see if there's any actual reason to think the bug is probably gone, or else, to atleast ask the submitter "Has anyone tested this with a current release ? Is it still relevant?" *then* close it if 3 weeks later there's been no response.