Closed Bug 1908317 Opened 4 months ago Closed 4 months ago

Firefox 128ESR no longer plays videos on Solaris - version 115ESR was ok

Categories

(Core :: Audio/Video: Playback, defect)

Firefox 128
defect

Tracking

()

RESOLVED FIXED
130 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- fixed
firefox128 --- wontfix
firefox129 --- wontfix
firefox130 --- fixed

People

(Reporter: petr.sumbera, Assigned: petr.sumbera)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file, 1 obsolete file)

Steps to reproduce:

Firefox 128ESR no longer plays videos on Solaris - version 115ESR was ok.

Last working version was 116.01a. Where my old binary from 2023-06-19 (0d3d276273c4) is ok and binary from 2023-06-20 (d8571e33cdd0) is bad.

It just says: "No video with supported format and MIME type found".

Tested with: https://tekeye.uk/html/html5-video-test-page
(youtube doesn't work too)

Unfortunately above hg hashes (hg id) are no longer recognized?!!!

Mike, do you please have any idea why old hg id hashes are no longer valid with current source repo? Or possibly what might have been the change which caused this regression?

Flags: needinfo?(mh+mozilla)

The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video: Playback' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core
Severity: -- → S3

Mike, do you please have any idea why old hg id hashes are no longer valid with current source repo?

The real question would be where did you get them. Are you keeping your source in Mercurial and is it patched? Because neither of the ids you gave exist in our repos AFAICT (and no, repos haven't changed).

Flags: needinfo?(mh+mozilla)

(In reply to Mike Hommey [:glandium] from comment #3)

The real question would be where did you get them. Are you keeping your source in Mercurial and is it patched? Because neither of the ids you gave exist in our repos AFAICT (and no, repos haven't changed).

Thank you!. This was my bad I do have there extra patches (commits)...

I was able to bisect it to like this.

The first bad revision is:
changeset: 668485:e608dfe11fc7
user: Alexandre Lissy <lissyx+mozillians@lissyx.dyndns.org>
date: Tue Jun 20 10:23:23 2023 -0700
description:
Bug 1835804 - Completely block from doing audio decoding on Content and RDD r=alwu

Keywords: regression
Regressed by: 1835804

(In reply to Petr Sumbera from comment #5)

I was able to bisect it to like this.

The first bad revision is:
changeset: 668485:e608dfe11fc7
user: Alexandre Lissy <lissyx+mozillians@lissyx.dyndns.org>
date: Tue Jun 20 10:23:23 2023 -0700
description:
Bug 1835804 - Completely block from doing audio decoding on Content and RDD r=alwu

Yes well, this has been here for a while. Are you sure Utility process is working correctly? Unfortunately, given the status of Solaris, I cannot debug that.

Flags: needinfo?(petr.sumbera)

Yes well, this has been here for a while. Are you sure Utility process is working correctly? Unfortunately, given the status of Solaris, I cannot debug that.

What is Utility process? And how can I verify it's working correctly? And yes I know I realized this late...

Flags: needinfo?(petr.sumbera)

(In reply to Petr Sumbera from comment #7)

Yes well, this has been here for a while. Are you sure Utility process is working correctly? Unfortunately, given the status of Solaris, I cannot debug that.

What is Utility process? And how can I verify it's working correctly? And yes I know I realized this late...

I dont get it, have you not hit the problem on release since last year ?
Utility is a new set of processes, one of them holding audio decoding.

Check about:processes to verify, but I am wondering if all we need is not just enabling in https://searchfox.org/mozilla-central/rev/b220e40ff2ee3d10ce68e07d8a8a577d5558e2a2/modules/libpref/init/StaticPrefList.yaml#10462-10479 ?

(In reply to :gerard-majax from comment #8)

(In reply to Petr Sumbera from comment #7)

Yes well, this has been here for a while. Are you sure Utility process is working correctly? Unfortunately, given the status of Solaris, I cannot debug that.

What is Utility process? And how can I verify it's working correctly? And yes I know I realized this late...

I dont get it, have you not hit the problem on release since last year ?

We do use ESR versions only. So I haven't noticed it. I do build nightly builds but with very limited testing...

This sounds very similar to bug 1886654: the lack of correlation between what the prefs say and what the code expects.

(In reply to Petr Sumbera from comment #10)

(In reply to :gerard-majax from comment #8)

(In reply to Petr Sumbera from comment #7)

Yes well, this has been here for a while. Are you sure Utility process is working correctly? Unfortunately, given the status of Solaris, I cannot debug that.

What is Utility process? And how can I verify it's working correctly? And yes I know I realized this late...

I dont get it, have you not hit the problem on release since last year ?

We do use ESR versions only. So I haven't noticed it. I do build nightly builds but with very limited testing...

Ok I was assuming you tested / used more the nightlies. I guess just switch the pref in about:config ? And at build time in the yaml file, once you have checked, we can land a patch. It worked without much complains on OpenBSD as well as FreeBSD (checked myself there) so hopefully Solaris should be easy as well

Unfortunately enabling media.utility-process.enabled (which was indeed false) didn't help. Tested on first bad commit with about:configchange and with 128.0 release and modification to modules/libpref/init/StaticPrefList.yam.

(In reply to Petr Sumbera from comment #13)

Unfortunately enabling media.utility-process.enabled (which was indeed false) didn't help. Tested on first bad commit with about:configchange and with 128.0 release and modification to modules/libpref/init/StaticPrefList.yam.

You need to verify if utility process is working. Try MOZ_LOG=utilityproc:5 to maybe start collecting data? Can you verify by just playing a simple audio file? Can you make sure you run that on a debug build ?

(In reply to Petr Sumbera from comment #13)

Unfortunately enabling media.utility-process.enabled (which was indeed false) didn't help. Tested on first bad commit with about:configchange and with 128.0 release and modification to modules/libpref/init/StaticPrefList.yam.

Sorry. about:config change on 128 worked...

Sorry. about:config change on 128 worked...

I wonder why following didn't worked:

--- firefox-128.0/modules/libpref/init/StaticPrefList.yaml
+++ firefox-128.0/modules/libpref/init/StaticPrefList.yam
@@ -10124,6 +10124,8 @@
   value: true
 #elif defined(XP_OPENBSD)
   value: true
+#elif defined(XP_SOLARIS)
+  value: true
 #else
   value: false
 #endif

Maybe XP_SOLARIS need to be defined for yaml somewhere...

(In reply to Petr Sumbera from comment #16)

Sorry. about:config change on 128 worked...

I wonder why following didn't worked:

--- firefox-128.0/modules/libpref/init/StaticPrefList.yaml
+++ firefox-128.0/modules/libpref/init/StaticPrefList.yam
@@ -10124,6 +10124,8 @@
   value: true
 #elif defined(XP_OPENBSD)
   value: true
+#elif defined(XP_SOLARIS)
+  value: true
 #else
   value: false
 #endif

Maybe XP_SOLARIS need to be defined for yaml somewhere...

is it working elsewhere? At least it's a relief if it works and we just need to fix the define ...

Sorry again. I was enabling media.rdd-process.enabled instead. So I expect XP_SOLARIS is working. I'm will check it...

Attached patch Bug1908317.patch (obsolete) — Splinter Review

Ok, actually both media.rdd-process.enabled and media.utility-process.enabled need to be set to true so that I can play videos.

Therefore I have set also all media.rdd-* as BSDs do.

Can you please integrate it? Ideally also into 128 branch.

Thank you both!

Can you submit it via Phab? I can approve and ask for uplift

Assignee: nobody → petr.sumbera

Comment on attachment 9414053 [details]
Bug 1908317 - Add XP_SOLARIS to media-related prefs r?padenot!

ESR Uplift Approval Request

  • If this is not a sec:{high,crit} bug, please state case for ESR consideration: Solaris maintainer mostly targets ESR
  • User impact if declined: No media playback working on Solaris
  • Fix Landed on Version: 130
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): Only flips prefs on Solaris, tested by Solaris maintainer
Attachment #9414053 - Flags: approval-mozilla-esr128?
Attachment #9413879 - Flags: approval-mozilla-esr128?
Attachment #9413879 - Flags: approval-mozilla-esr128?
Attachment #9413879 - Attachment is obsolete: true
Pushed by alissy@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8c746156d7c5 Add XP_SOLARIS to media-related prefs r=padenot

Thank you very much for fixing this. I just wonder whether setting media.audioFocus.management for Solaris is intentional?

(In reply to Petr Sumbera from comment #26)

Thank you very much for fixing this. I just wonder whether setting media.audioFocus.management for Solaris is intentional?

I took your patch as-is, I made no change at all

Status: UNCONFIRMED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch

Set release status flags based on info from the regressing bug 1835804

(In reply to :gerard-majax from comment #27)

(In reply to Petr Sumbera from comment #26)

Thank you very much for fixing this. I just wonder whether setting media.audioFocus.management for Solaris is intentional?

I took your patch as-is, I made no change at all

That shouldn't be enabled on Solaris. That is only enabled by default on Android.

Flags: needinfo?(lissyx+mozillians)
Flags: needinfo?(lissyx+mozillians)

Backed out as requested by developer

Backout link

Status: RESOLVED → REOPENED
Ever confirmed: true
Flags: needinfo?(petr.sumbera)
Resolution: FIXED → ---
Target Milestone: 130 Branch → ---
Flags: needinfo?(petr.sumbera)
Pushed by alissy@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7d083d75388a Add XP_SOLARIS to media-related prefs r=padenot
Backout by nfay@mozilla.com: https://hg.mozilla.org/mozilla-central/rev/17630c12ac58 Backed out changeset 8c746156d7c5 as requested by developer CLOSED TREE

The backout was merged to central and then merged back to autoland. As a result of this, there's a chance this has to be relanded on autoland in order for it to get fixed. Here is the central revision for the backout: https://hg.mozilla.org/mozilla-central/rev/17630c12ac58

Flags: needinfo?(lissyx+mozillians)
Flags: needinfo?(lissyx+mozillians)

re-landed from phab, are we good?

Flags: needinfo?(nfay)
Pushed by alissy@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9aa5f8358ff3 Add XP_SOLARIS to media-related prefs r=padenot

Yes, that is fine

Flags: needinfo?(nfay)
Status: REOPENED → RESOLVED
Closed: 4 months ago4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch

Comment on attachment 9414053 [details]
Bug 1908317 - Add XP_SOLARIS to media-related prefs r?padenot!

Approved for 128.1esr.

Attachment #9414053 - Flags: approval-mozilla-esr128? → approval-mozilla-esr128+
Flags: qe-verify+
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: