https://bugs.winehq.org/show_bug.cgi?id=50779
--- Comment #22 from Zeb Figura z.figura12@gmail.com --- (In reply to Rafał Mużyło from comment #21)
SHA1 of the regression would require a bisect, which (for reasons) I haven't done.
What I did do (at least AFAIR - it's been over 1.5 years since already), was establish it happened at 6.1 exactly, then comb it for sound changes (as the bug was triggered upon sound effects playing), then with your help notice it was virtual mapping space exhaustion triggered by spawning multiple threads for each sound effect. That pretty much pointed towards the changeset containing 'winegstreamer: Manage our own streaming thread'. As that changeset was too complex to revert bit by bit (at least at my skill level), I've pretty much stopped there.
So you haven't actually proven anything. You made a guess, then didn't try to verify it at all.
If you're confident in that guess, you don't even need to perform a full bisect. All you need to do is check out that commit, test that you can reproduce the issue, then check out the previous commit and test that you can't. What part of this is infeasible?