This is why I will use the term, "issue", or
possible bug, myself. Only if I can reproduce the issue on-command, every time, then I will refer it as a bug.
Distinction in terms, however, downplays the importance in resolving issues.
So, I will introduce a new term for us all to use, that even CW can't ignore, because they do understand just what we mean:
Cursident - repeated unreasonable, unexpected result, that does not yet qualify to be a bug, but does qualify for support attention.
Incidents or anomalies, maybe even the occasional bug will raise an eyebrow, prompt a re-try, and "Carry-On". Two occurrences of the same thing (or similar to) will get a huff, three will garner a "wtf", but FOUR times, within one session will give us at least one curse-word. That's not enough to give us a "bug", but it sure feels like someone didn't do their homework, whether it be the computer-maker, Microsoft, CW, Audio/video hardware maker, subversive janitor (Anti-virus software), or the end user. In any case, unless the issue is the End-User, this shouldn't be the customer's problem, right? We paid for a solid product built on a foundation that has actually been tested and free of bugs, correct? Yet, we do live with the acceptance that bugs are simply a way of life, or the software developer companies won't remain competitive.
I think they're doing a pretty good job, but let's not stop at resolving bugs. Let's move on to resolve issues, or at least check out what could be the problem. CW should have developed some debugging tools to remain well inside Sonar, that could be enabled/disabled from a
separate program.exe, not from within Sonar. From that, we could let it run for a while and when the cursident occurs, we at least have a way to "snap-shot" Sonar and logs to report. And if the program crashes, the crash-reporter will have a few more options, some of which the more intelligent of us might actually be able to check out on our own.
But there you have it, cursident. By the fourth time you have an issue, it makes you curse, and that should be a cause to at least log the occurrence at CW.