This is just a NS_Warning when a VDA (hardware decoder) can't be created. depending on your hardware card, there's only a certain number of hardware decoders that can be created. A Mac mini 2010 can only open 4. When that happens, it will fall back to software decoding with Apple VideoToolbox framework instead. There's nothing wrong, it's behaving as designed. Or are you seeing something else like playback stopping?
(In reply to Jean-Yves Avenard [:jya] from comment #1) > This is just a NS_Warning when a VDA (hardware decoder) can't be created. It's an NS_ERROR, not an NS_WARNING isn't it? That's a critical error. Maybe it should be changed to something less fatal if it's a warning.
(In reply to Jean-Yves Avenard [:jya] from comment #1) > Or are you seeing something else like playback stopping? I did see some intermittent problems with the video was black or a frozen frame after I seeked to a new position, but might be the problem I reported in bug 1140690. Note that I only see these AppleVDADecoder assertion failures for the "Microsoft ##" videos. I selected a few other videos randomly and none of them hit this assertion.
I hit this assertion on YouTube, too, but not as easily as with the DASH-IF player's Microsoft videos.
NS_ERROR asserts on debug builds, not on release. So this doesn't affect users, but if it's expected behaviour we should change it to an NS_WARNING or a debug message.
use NS_WARNING, and update message to be more explicit
Assignee: nobody → jyavenard
Status: NEW → ASSIGNED
note that the inability to create a VDA decoder will be greatly reduced once bug 1128381 lands, as we now only use a single decoder at a time rather than one for every resolutions
use NS_WARNING, and update message to be more explicit v2
Attachment #8575797 - Flags: review?(giles)
Comment on attachment 8575797 [details] [diff] [review] Only print a warning when VDA decoder couldn't be created Looks good, thanks.
Attachment #8575797 - Flags: review?(giles) → review+
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
status-firefox39: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla39
You need to log in before you can comment on or make changes to this bug.