Thanks for the suggestion, but I would like to inform you that this is the procedure we follow. 

If the issues is not commented for long time then we close the issue with the reason being, we are continuously fixing issues and releasing new chrome version, so most of the times issues is already fixed in the new version.

Hope this explanation helps.

Thank you! 

> but I would like to inform you that this is the procedure we follow. 

I know that, I just would like you to realise how stupid it is.

> we close the issue with the reason being, we are continuously fixing 
> issues and releasing new chrome version, so most of the times issues 
> is already fixed in the new version.

"Most of the times"? Is that an assumption or a statistic?

Because most of the times (if not every single time) that I see an issue I starred or reported automatically closed, it is *not* fixed.

Also, if that is the reason, here's a suggestion for a better procedure:
- when the given timespan without comments expires, instead of closing the issue automatically, trigger some kind of alert requesting the assigned person for revision (if a year can pass by without a bug being even assigned, then you have another huge problem)
- somebody test the issue, and if it actually *is* closed, fix it.

Thank you for providing more feedback. Adding requester "ashejole@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Thanks for the feedback. We appreciate your suggestion. Marking the above issue as Untriaged as considering this as new feature request.

I hate that we still can't edit our own comments in this stupid, prehistoric-like bug tracker.

What I meant here:
> ... and if it actually *is* closed, fix it.

was obviously the other way round: "if it actually *is* fixed, close it"

Here's a fresh example: https://bugs.chromium.org/p/chromium/issues/detail?id=163745