https://bugs.winehq.org/show_bug.cgi?id=43125
--- Comment #13 from Konrad Rzepecki hannibal@astral.lodz.pl ---
I'd like to fix this in two steps:
- Make the message less spammy: Only display the message once as long as
there are no readers in irp_queue.
I think this is not needed if you apply 2. This will require unnecessary code running at each call.
- Degrade the message to debug log level: As far as I understand the code
and the logic behind the delivery design, having no readers for incoming reports is not an error condition. It's a warning at most, and a pretty uninteresting even unless you're debugging things.
Good idea.
I wonder if this message isn't an artifact form time when this code was not placed in critical section...