On Wed Feb 25 18:50:59 2026 +0000, Elizabeth Figura wrote:
I don't really understand why we're doing this in the first place. The documentation often claims things that are wrong especially as related to edge cases. If there's not a foreseeable case where RtlGenRandom() could fail (and I don't think memory exhaustion counts as foreseeable either) then I don't think it's worth touching. The documentation is right as far as I'm aware and the whitepaper explains that it was an intentional decision that people can rely on. So I do think that wine should behave as close to Windows as reasonably possible.
And after looking at it closer I think wine already does exhibit the same behaviour in practice. So I'm coming round to the idea that this doesn't need to be handled in `ProcessPrng`. I am thinking it might be appropriate to more strongly guarantee this at the actual point where we return an error, e.g. https://gitlab.winehq.org/cdenton/wine/-/commit/93ed99966b316f4c9c1e03af7de5... -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10174#note_130522