@jarmer I can't say officially what the response from Google is as the response is not coming from Google's PR team or some such and I don't want to break my relationship or disrespect anyone..
Basically Google's engineers need consistent steps to replicate the bug for them to elevate the priority of the issue. So let's try help them get that so we can get this sorted!
That's a tough one, although it happens regularly. It doesn't happen "every single time"
In that post there are error logs posted, exact steps duplicated, and even a video posted by a user showing exactly what's happening. I'm not sure how much more detailed we can even get. This just seems to be completely ignored by google. There are lots of "hey google, what's up?" with no response.
@Nephiel hmmm that's awesome! Thanks very much for posting. I do have root, but, I really don't want to disrupt the normal battery features of Marshmallow, so I will hold off for now and just hope for the best with an official patch.