I have posted a couple questions like this: Code can stop working with compiler optimization
All of them have been closed. I can see why this question may be perceived as too broad, but I think that should only be faulted on the asker if they CANNOT narrow their question. I don't have a whole lot of information to go on and the bug I am encountering is very confusing and elusive. I'm not sure what causes it, if I did I wouldn't need to ask what might be causing it, I'd just fix it myself. I understand that answers are shots in the dark but the answers I have gotten have at least given me places to look in my code for where the problem may lie and I think that if my questions were to remain open, an answer would eventually lead me in the right direction. As it is, I know I am getting closer to a solution with help from Stack Oveflow's users so why close a productive question just because it is difficult to answer definitively?
The bottom line is I'm probably doing something wrong in my code and Stack Overflow is helping me figure out what. The discussion is productive, so I see no reason for it to be closed. Although my issue is hard to define, I am actively trying to narrow the problem. If I could make my question any more clear I would.
What message are you sending here? I can only get help from Stack Overflow on questions that aren't too difficult to answer?