http://bugs.winehq.org/show_bug.cgi?id=17955
--- Comment #49 from Anton Vorobyov phoenix@mail.ru 2009-08-26 10:56:03 --- Crash occurred for me one time each 2-6 hours. With new git version - eve was running more than 25-30 hours without any crashes. I believe i can operate probabilities not worse than average IT guy, and from my perspective - chance is less than 2-5% that crash is still here. And that's the reason why i left note to wait until new tag is made and couple of other guys confirm this.
Actually resources of Wine developers and community are limited. What you described - is right way to do, but it's utopia unless YOU get it in your own hands and find exact repro steps and reason why we experienced these crashes. In real world when working on big projects (my current job is QA Team Lead in the biggest casual games company - Oberon Media) like Wine developers can't spend their time finding source of each and every bug, especially when reporter has no clue by which module it is caused.
To keep bug tracker clean it's good idea to close such 'random' issues if nobody gets it for some time (time is chosen dependant upon available qa resources and other project specifics).
I've just added one bit of statistics to the whole picture. When other guys (who experienced that crash before) will also tell that it seems to be fixed - bug may be safely closed. In the end of the day, you always have an option to reopen it.