tl;dr: Please get rid of "This question has an open bounty and cannot be closed"
Questions with bounties on them can't be closed:
But why should a bounty disable regular community moderation?
We should be able to cast close votes on bountied questions as usual, and if a question gets enough, the bounty's refunded and the question closed.
An obvious benefit would be reduced burden on moderators, but I doubt that this is really a significant part of their workload. More important is allowing the entire community's wisdom to be brought to bear.
Consider this question: Some bottleneck OS resource
Having a simple MFC application with web browser controller that navigates to some site and then to another one on and on.
Using a powerfull machine (16 cores and lots of memory) OS is Server 2008 R2. I can see when launching my app over 30 instances I'm getting the OS UI (each window including my app, mspaint, taskmgr etc..) become very sluggish and slow.
I have monitored the machine resources (CPU, memory and GDI objects) but it seems that all of them are not even close to be in some level of stress.
What is the problematic resource that influence the machine in such way?
It doesn't look like a good question: somewhat poorly written, vague, not a ton of information, etc. I would vote to close this question. However, I don't do much work with MFC and maybe there's something I'm missing. (I can readily imagine a similarly bad looking question with the extremely concrete answer: CPython's Global Interpreter Lock.)
I'm comfortable casting a vote to close, not closing unilaterally. Flagging for a moderator just passes the buck to them, when the correct action is letting the community weigh in.