https://bugs.winehq.org/show_bug.cgi?id=55143
--- Comment #15 from Zeb Figura z.figura12@gmail.com --- (In reply to Rafał Mużyło from comment #11)
The message itself isn't, but there also a function, that definitely is implemented, is reported as missing due to using delayed load mechanism.
Yes. There are also far more likely ways for that to be the case than address space exhaustion.
Failure to load winegstreamer is unlikely to be due to address space exhaustion because it is far more likely to be due to winegstreamer never having been compiled.
Failure to load uxtheme is unlikely to be due to address space exhaustion because it is loaded almost immediately during user32 initialization.
As for being a nag, I only do that if I receive no valid feedback *and* I'm nearly sure I have a good point. In that particular case, the bug is over 6 months old *and* that first patch almost certainly does what the API docs tell it's supposed to do (as a random bonus, the main part of that particular bug - unrelated to the patches - is about dying due to excessive memory consumption by graphics).
No, you misunderstand. I did not say "stop bringing up unrelated bugs unless you feel entitled to a response". I said "stop bringing up unrelated bugs". Period.
Yes, sometimes your bug goes unexamined for months or even years. That is the consequence of reporting bugs to a volunteer-driven project. It is especially the consequence when you consistently ignore the bug tracker directions, or requests for information, because you think you know better.