celenity/Phoenix
8
198
Fork
You've already forked Phoenix
19

[WEB COMPAT] Videos won't load on X.com/Nitter.net #282

Closed
opened 2026年04月29日 10:44:00 +02:00 by ViperTheRipper · 12 comments

Confirmation Checklist

Which domain(s) are you experiencing this issue on?

X.com (akka Twitter) and nitter.net

What web browser(s) are you using with Phoenix?

IronFox

Other

No response

What operating system(s) are you experiencing this issue on?

Android

Other

No response

What version of Firefox/Gecko and Phoenix are you using?

IronFox v150.0 (Build #2016156658)

If you remember, what version of Firefox/Gecko and Phoenix did you first notice the issue on?

No response

Does the issue occur on a new browser profile?

  • Yes
  • No

Please share your browser's distribution ID.

No response

Please share your browser's update channel.

browser.ironfox.channel - release

Please share a list of your currently installed browser add-ons/extensions, as well as the versions you have installed.

uBlock Origin

Please explain the issue you are experiencing.

The videos aren't played on x.com, nor on similar clients like Nitter.net

Please provide detailed steps to reproduce the issue.

Visit x.com/nitter.net and try to play a video from a tweet: The video fails to load.
Disabling uBO doesn't change this state, the video still fails to load.
Automatic media playback is set by default.

### Confirmation Checklist - [x] I confirm that this issue occurs on the **latest release** of Phoenix. You can check what the latest version is on [the `Releases` page](https://codeberg.org/celenity/Phoenix/releases). - [x] I confirm that this issue is **NOT** already listed on [the Website Compatibility wiki page](https://phoenix.celenity.dev/compat). - [x] I confirm that this issue has **NOT** already been reported on [the Codeberg issue tracker](https://codeberg.org/celenity/Phoenix/issues), [the GitLab issue tracker](https://gitlab.com/celenityy/Phoenix/-/issues), **and/or** [the GitHub issue tracker](https://github.com/celenityy/Phoenix/issues). ### Which domain(s) are you experiencing this issue on? X.com (akka Twitter) and nitter.net ### What web browser(s) are you using with Phoenix? IronFox ### Other _No response_ ### What operating system(s) are you experiencing this issue on? Android ### Other _No response_ ### What version of Firefox/Gecko and Phoenix are you using? IronFox v150.0 (Build #2016156658) ### If you remember, what version of Firefox/Gecko and Phoenix did you first notice the issue on? _No response_ ### Does the issue occur on a new browser profile? - [x] Yes - [ ] No ### Please share your browser's distribution ID. _No response_ ### Please share your browser's update channel. browser.ironfox.channel - release ### Please share a list of your currently installed browser add-ons/extensions, as well as the versions you have installed. uBlock Origin ### Please explain the issue you are experiencing. The videos aren't played on x.com, nor on similar clients like Nitter.net ### Please provide detailed steps to reproduce the issue. Visit x.com/nitter.net and try to play a video from a tweet: The video fails to load. Disabling uBO doesn't change this state, the video still fails to load. Automatic media playback is set by default.

It's happening in my environment too.
When I looked at the debugger console while accessing the direct video link (twimg.com), I saw this kind of warning. (The video is just a random one I posted previously)

Media resource https://video.twimg.com/amplify_video/1957541485844525061/vid/avc1/1280x720/dNAqtPrSAU8h81ig.mp4?tag=14 could not be decoded, error: Error Code: NS_ERROR_DOM_MEDIA_METADATA_ERR (0x806e0006)

Reinstalling Ironfox temporarily fixed the issue, but it started happening again after a while (I don't remember exactly, but I think it was about a day later).

It's happening in my environment too. When I looked at the debugger console while accessing the direct video link (twimg.com), I saw this kind of warning. (The video is just a random one I posted previously) ``` Media resource https://video.twimg.com/amplify_video/1957541485844525061/vid/avc1/1280x720/dNAqtPrSAU8h81ig.mp4?tag=14 could not be decoded, error: Error Code: NS_ERROR_DOM_MEDIA_METADATA_ERR (0x806e0006) ``` Reinstalling Ironfox temporarily fixed the issue, but it started happening again after a while (I don't remember exactly, but I think it was about a day later).

@ViperTheRipper @c2qd Thanks for the report!

Can either of you please provide a link to a specific video where this is happening? I'm unable to replicate from my end.

@ViperTheRipper @c2qd Thanks for the report! Can either of you please provide a link to a specific video where this is happening? I'm unable to replicate from my end.

@celenity wrote in #282 (comment):

Can either of you please provide a link to a specific video where this is happening? I'm unable to replicate from my end.

It happens with any video. (To give an example, this one mentioned earlier.) However, I'm not really sure what actions cause it to occur. Considering it didn't happen for a while after re-installing, it might occur after watching a lot of videos, but that's just a possibility.
Once it occurs, it becomes impossible to watch any video after that due to the same error.

@celenity wrote in https://codeberg.org/celenity/Phoenix/issues/282#issuecomment-14209517: > Can either of you please provide a link to a specific video where this is happening? I'm unable to replicate from my end. It happens with any video. (To give an example, [this one](https://video.twimg.com/amplify_video/1957541485844525061/vid/avc1/1280x720/dNAqtPrSAU8h81ig.mp4?tag=14) mentioned earlier.) However, I'm not really sure what actions cause it to occur. Considering it didn't happen for a while after re-installing, it might occur after watching a lot of videos, but that's just a possibility. Once it occurs, it becomes impossible to watch any video after that due to the same error.

I am not certain of @ViperTheRipper's specific situation, but in my case, the issue was caused by enabling isolatedProcesses. I sincerely apologize; I had completely overlooked that detail.
@ViperTheRipper, perhaps you should check your hidden settings just to be safe.


(削除) Interestingly, it appears that when media.rdd-process.enabled is set to true, playback proceeds without error even if isolatedProcesses is enabled.
ref. https://bugzilla.mozilla.org/show_bug.cgi?id=1887735 (削除ここまで)

related: 752d17bb34

I am not certain of @ViperTheRipper's specific situation, but in my case, the issue was caused by enabling isolatedProcesses. I sincerely apologize; I had completely overlooked that detail. @ViperTheRipper, perhaps you should check your hidden settings just to be safe. --- ~~Interestingly, it appears that when `media.rdd-process.enabled` is set to `true`, playback proceeds without error even if isolatedProcesses is enabled. ref. https://bugzilla.mozilla.org/show_bug.cgi?id=1887735~~ related: https://codeberg.org/celenity/Phoenix/commit/752d17bb34e5d241424802e516cec7c8550148c0

@celenity wrote in #282 (comment):

@ViperTheRipper @c2qd Thanks for the report!

Can either of you please provide a link to a specific video where this is happening? I'm unable to replicate from my end.

Sorry for the delay in replying. 🙃

I was getting an error on every video on x.com/nitter.net. Over the last few days I tried different settings to see what might be breaking playback, and, as @c2qd mentioned 🫡, it turned out to be related to process isolation. Luckily I had a second device where this didn't happen. Both phones had process isolation enabled, but only one had media.rdd-process.enabled set to "true". The device that failed had it set to "false". I changed it ... et voilà!! it's working again.
If I remember correctly, this setting was disabled in recent updates...🤔 (sorry for not testing this with a clean install, but my saved bookmarks are enormous and I've applied dirty-updates in the latest versions).

PS: looking forward to a local bookmark export 🤞.

Thanks a lot @celenity and @c2qd for your support and quick replies 😎.

@celenity wrote in https://codeberg.org/celenity/Phoenix/issues/282#issuecomment-14209517: > @ViperTheRipper @c2qd Thanks for the report! > > Can either of you please provide a link to a specific video where this is happening? I'm unable to replicate from my end. Sorry for the delay in replying. 🙃 I was getting an error on every video on x.com/nitter.net. Over the last few days I tried different settings to see what might be breaking playback, and, as @c2qd mentioned 🫡, it turned out to be related to process isolation. Luckily I had a second device where this didn't happen. Both phones had process isolation enabled, but only one had media.rdd-process.enabled set to "true". The device that failed had it set to "false". I changed it ... et voilà!! it's working again. If I remember correctly, this setting was disabled in recent updates...🤔 (sorry for not testing this with a clean install, but my saved bookmarks are enormous and I've applied dirty-updates in the latest versions). PS: looking forward to a local bookmark export 🤞. Thanks a lot @celenity and @c2qd for your support and quick replies 😎.

@ViperTheRipper wrote in #282 (comment):

Both phones had process isolation enabled, but only one had media.rdd-process.enabled set to "true". The device that failed had it set to "false". I changed it ... et voilà!! it's working again.
If I remember correctly, this setting was disabled in recent updates...🤔 (sorry for not testing this with a clean install, but my saved bookmarks are enormous and I've applied dirty-updates in the latest versions).

We currently don't recommend enabling media.rdd-process.enabled on Android - we disabled it because we found it was leading to memory safety issues, which can create privacy and security issues. We instead recommend disabling isolated process for now and keeping media.rdd-process.enabled off until these issues are resolved and its ready/more mature.

@ViperTheRipper wrote in https://codeberg.org/celenity/Phoenix/issues/282#issuecomment-14452979: > Both phones had process isolation enabled, but only one had media.rdd-process.enabled set to "true". The device that failed had it set to "false". I changed it ... et voilà!! it's working again. > If I remember correctly, this setting was disabled in recent updates...:thinking: (sorry for not testing this with a clean install, but my saved bookmarks are enormous and I've applied dirty-updates in the latest versions). We currently don't recommend enabling `media.rdd-process.enabled` on Android - we disabled it because we found it was [leading to memory safety issues](https://codeberg.org/ironfox-oss/bugs/issues/236), which can create privacy and security issues. We instead recommend disabling isolated process for now and keeping `media.rdd-process.enabled` off until these issues are resolved and its ready/more mature.

Thanks for the clarification @celenity ; the thread has been reopened.

I have currently set media.rdd-process.enabled back to false again, and the error persists with every single video I attempt to play from X.com or Nitter.net. For example: https://x.com/CollinRugg/status/2053484088192061659?ref_src=twsrc^tfw / https://nitter.net/CollinRugg/status/2053484088192061659#m.

isabling uBO makes no difference, just as when I set Isolated Content Processes to off as @c2qd suggested. Separately, I’ve noticed that when I log in to GitHub or Outlook, my accounts remain active after I exit IronFox—except when I force-close the application (all the 'Clear data on exit' boxes are checked)

Thanks again for all your amazing work! 👍

Thanks for the clarification @celenity ; the thread has been reopened. I have currently set `media.rdd-process.enabled` back to `false` again, and the error persists with every single video I attempt to play from X.com or Nitter.net. For example: https://x.com/CollinRugg/status/2053484088192061659?ref_src=twsrc^tfw / https://nitter.net/CollinRugg/status/2053484088192061659#m. isabling uBO makes no difference, just as when I set Isolated Content Processes to off as @c2qd suggested. Separately, I’ve noticed that when I log in to GitHub or Outlook, my accounts remain active after I exit IronFox—except when I force-close the application (all the 'Clear data on exit' boxes are checked) Thanks again for all your amazing work! 👍

@ViperTheRipper

I have currently set media.rdd-process.enabled back to false again, and the error persists with every single video I attempt to play from X.com or Nitter.net.

To confirm, is this also with isolated process disabled?

Also, from about:config, can you please confirm that media.android-media-codec.enabled is set to true?

Thank you for your time and support!

@ViperTheRipper > I have currently set `media.rdd-process.enabled` back to `false` again, and the error persists with every single video I attempt to play from X.com or Nitter.net. To confirm, is this also with isolated process disabled? Also, from [`about:config`](about:config), can you please confirm that `media.android-media-codec.enabled` is set to `true`? Thank you for your time and support!
  • Set media.android-media-codec.enabled to true + isolated processes enabled = Videos are playing without problems.
  • Set media.android-media-codec.enabled to false + isolated processes enabled = "The media could not be played" error.
  • Set media.android-media-codec.enabled to false + isolated processes disabled = Videos are playing without problems.
- Set media.android-media-codec.enabled to true + isolated processes enabled = Videos are playing without problems. - Set media.android-media-codec.enabled to false + isolated processes enabled = "The media could not be played" error. - Set media.android-media-codec.enabled to false + isolated processes disabled = Videos are playing without problems.

@ViperTheRipper wrote in #282 (comment):

  • Set media.android-media-codec.enabled to true + isolated processes enabled = Videos are playing without problems.

    • Set media.android-media-codec.enabled to false + isolated processes enabled = "The media could not be played" error.

    • Set media.android-media-codec.enabled to false + isolated processes disabled = Videos are playing without problems.

Apologies for the late response - Thanks for clearly laying this out.

To confirm, what happens if media.android-media-codec.enabled is true and isolated process is disabled?

@ViperTheRipper wrote in https://codeberg.org/celenity/Phoenix/issues/282#issuecomment-14957013: > * Set media.android-media-codec.enabled to true + isolated processes enabled = Videos are playing without problems. > > * Set media.android-media-codec.enabled to false + isolated processes enabled = "The media could not be played" error. > > * Set media.android-media-codec.enabled to false + isolated processes disabled = Videos are playing without problems. Apologies for the late response - Thanks for clearly laying this out. To confirm, what happens if `media.android-media-codec.enabled` is `true` and isolated process is disabled?

Of course, setting media.android-media-codec.enabled to true + isolated processes disabled = Video are playing without problems.

Sorry @celenity 😉

EDITED: Memory lapse 🤯

Of course, setting media.android-media-codec.enabled to true + isolated processes disabled = Video are playing without problems. Sorry @celenity 😉 EDITED: Memory lapse 🤯

@ViperTheRipper wrote in #282 (comment):

Of course, setting media.android-media-codec.enabled to true + isolated processes disabled = Video are playing without problems.

Sorry @celenity 😉

EDITED: Memory lapse 🤯

Thanks for confirming! It looks to me like this is working as expected in that case, so I'll go ahead and close this - but please let me know if you have any further issues. Hopefully upstream improves the RDD process implementation on Android, so that we can enable it by default in the future (and thus also enable isolated process by default for IronFox, without breaking media playback).

@ViperTheRipper wrote in https://codeberg.org/celenity/Phoenix/issues/282#issuecomment-15855065: > Of course, setting media.android-media-codec.enabled to true + isolated processes disabled = Video are playing without problems. > > Sorry @celenity :wink: > > EDITED: Memory lapse :exploding_head: Thanks for confirming! It looks to me like this is working as expected in that case, so I'll go ahead and close this - but please let me know if you have any further issues. Hopefully upstream improves the RDD process implementation on Android, so that we can enable it by default in the future *(and thus also enable isolated process by default for IronFox, without breaking media playback)*.
Sign in to join this conversation.
No Branch/Tag specified
dev
pages
2026年07月08日.1
2026年06月10日.1
2026年05月21日.2
2026年05月21日.1
2026年04月27日.1
2026年03月31日.1
2026年03月30日.1
2026年02月23日.1
2026年02月16日.1
2026年01月21日.1
2025年12月23日.1
2025年11月27日.1
2025年11月07日.1
2025年10月26日.1
2025年10月12日.1
2025年10月03日.1
2025年09月07日.1
2025年08月06日.1
2025年07月30日.1
2025年07月11日.1
2025年06月24日.1
2025年06月12日.1
2025年06月10日.1
2025年06月06日.1
2025年06月02日.2
2025年06月02日.1
2025年05月11日.1
2025年04月27日.1
2025年04月15日.1
2025年04月11日.1
2025年04月02日.1
2025年03月25日.1
2025年03月20日.1
2025年03月12日.1
2025年03月05日.1
2025年02月28日.1
2025年02月21日.1
2024年02月18日.1
2025年02月14日.1
2025年02月13日.1
2025年02月01日.1
2025年01月30日.1
2025年01月27日.1
2025年01月24日.1
2025年01月22日.2
2025年01月22日.1
2025年01月20日.2
2025年01月20日.1
2025年01月19日.1
2025年01月14日.1
2025年01月13日.1
2025年01月12日.2
2025年01月12日.1
2025年01月06日.1
05January2025v1
20240103.2
20250103.1
20241229-1
20241225-1
20241216-1
20241211-1
20241204-1
20241203-1
31November2024v1
20241103-1
20240924-1
20240914-1
20240907-1
20240902-1
20240831-1
20240825-1
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
celenity/Phoenix#282
Reference in a new issue
celenity/Phoenix
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?