I don't think it is a waste of time at all. We are skilled, friendly and quite quick to reply depending on the time of the week. Recreating and logging bugs is a really important part of our job and I appreciate and value every one that takes time to report issues.
For a bug to get past us to the developers it needs to be reproducible, otherwise it is just a story and while it gets investigated it will not be reported as a bug until several users reports the same behaviour.
This is not a bug yet. This is a story. It can be a user error, a conceptual error, a hardware fault or something external affecting it. There is more information and investigation needed since it did not happen to me the 10 times I just tried with these instructions. I'm not dismissing your report at all but we need to find a way to recreate it.
A lot of reported "bugs" are not bug but user errors. We all have a very different idea of how the unit shall work. There can be a lot of pride in people in this industry and when reporting an issue we all(including me) need to have our mind set to that we can be wrong or that there are other limitations or concepts that can cause these issues.
Last I want to say. Even though I lurk and read almost every post here the forum is not the way to report bugs. Collect, discuss, challenge(really important) each others stories and then report to support. A story or anecdote that cannot be confirmed needs to be looked at with caution as it's a good way to spread rumours.
This is a good story that has value. I have my suspicions and a project where it happens every time is good place to start. (PM me or create a case)