Some media (usually GIFs) won't play after hibernation
Categories
(Core :: Graphics, defect, P3)
Tracking
()
People
(Reporter: agressorini, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:120.0) Gecko/20100101 Firefox/120.0
Steps to reproduce:
Hard to catch - my routine is to open FF, and use it normally for a few days. Usually meantime there are hibernation\sleeps.
After resuming the system and Firefox some websites like Discord won't show GIFs anymore - their gif browser is empty.
Actual results:
An empty gif browser, empty posts. I checked the console and has a lot stuff which belong to:
MediaLoadExhaustedCandidates
Invalid URI. Load of media resource %S failed
I use other language than English so I took only string names from the language file but maybe it would be handy so I paste the original texts:
Element <source> nie ma atrybutu „src”. Treść multimedialna nie została wczytana.
Żaden z potencjalnych zasobów multimedialnych nie mógł zostać wczytany. Wczytywanie multimediów wstrzymane.
Metoda „MouseEvent.mozInputSource” jest przestarzała. Zamiast niej należy korzystać z „PointerEvent.pointerType”.
Nieprawidłowy adres URI. Treść multimedialna „” nie została wczytana.
The problem started around the infamous FF bugs with youtube (around FF 102 or 103) and is present till today. Firefox 101 works OK.
I have used a copied profile - no better.
I have created a new profile and no better.
Furthermore, I have thought it was related to cache, memory but I doubt it now. It does happen mostly after some hibernations (sometimes 1, sometimes a few are required). It is hard to catch.
After closing FF and reopening it the problem is gone.
Expected results:
It should show and play gifs.
|
||
Comment 1•2 years ago
|
||
I could not reproduce it on Win10x64 using Firefox build 120.0.
Forsberg, can you please mention what language are you using? Thank you.
(In reply to Monica Chiorean from comment #1)
I could not reproduce it on Win10x64 using Firefox build 120.0.
Forsberg, can you please mention what language are you using? Thank you.
Hey, it is hard to catch to be honest. Sometimes it takes a one day, then I restart the app, it works for 3 days without issues and for the fourth day it gets broken. It looks like something builds up or so.
Previously I thought it might be related to http3, cache, memory or broken profile but am not sure anymore. Because it can takes a few hibernations\days to get such an error it may take a while to catch more symptoms. For now I disabled OpenGL and hardware acceleration but I doubt it would be that tbh.
I use the Polish language.
|
||
Comment 3•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: Core & HTML' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
I have more feedback.
I am testing hardware acceleration on and off. Been testing OFF for about a week and during this time I had no hibernation/gif media playback issues. I had to restart FF twice or so but I doubt it could have had impact here.
The question is how can it be related to media playback and what changed in FF 102 and up that it got broken.
Other issue is that FF cannot let to use hardware acceleration per site, it is only a global value for all or for none.
|
||
Comment 5•2 years ago
|
||
This doesn't look like a DOM bug, move to image to see if people there has some idea.
|
||
Comment 6•2 years ago
|
||
This doesn't feel like imagelib. The errors mentioned are Media*. Inspecting the gif browser on discord they are not images but mp4s.
You are right. GIF is the old name, they may just use mp4s but old boomers like me still call it GIFs. I enabled hardware acceleration and of course it stopped working after some time. All mp4s from Discord and other sites as well - mp4 players are blank. My console shows such errors: Using the synchronous version of the XMLHttpRequest method on the main thread is deprecated due to harmful side effects.
jQuery.Deferred exception: $reference_div.offset() is undefined $.fn.alwaysOnScreen@https
Uncaught TypeError: $reference_div.offset() is undefined
Is there any low level of debug possible to track it down?
By another site such errors when trying to play a movie/gif (mp4 I think).
Loading failed for element 'script' with source
The "ihmn" cookie does not have a corresponding value for the "SameSite" attribute. Soon, cookies without the "SameSite" attribute or with an invalid value will be treated according to the "Lax" rule. This means that the cookie will no longer be sent in external website contexts. If your application requires this cookie to be available in such contexts, please add the "SameSite=None" attribute to it. https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite has more information about the "SameSite" attribute inject.a6006ca5d4db5952d938.js:1:1412
Feature Policy: Skipping unsupported feature name ("autoplay").
Feature Policy: Suppress unsupported feature name ("encrypted-media").
Feature Policy: Skipping unsupported feature name ("autoplay").
Feature Policy: Suppress unsupported feature name ("encrypted-media").
A partitioned cookie or storage access has been granted for "https://streamable.com/t/32uofk" because it is loaded in the context of an external site and dynamic state partitioning is enabled.
Some cookies misuse the recommended "SameSite" attribute 8
Firefox cannot connect to the wss://socket.streamable.com/ server. 32uofk:1115:61
49 21ms: Websocket error: [object Event]
|
|
||
Comment 9•2 years ago
|
||
Does the problem happen in safe mode or a fresh profile?
There's probably something specific to your configuration involved since we haven't seen widespread reports of this AFAIK.
|
Reporter | |
Comment 10•2 years ago
|
||
Yes, the issue is on the fresh profile as well. With disabled hardware acceleration there are no issues. But I cannot understand what the hardware acceleration would have had to do with it... and why it doesn't stop at once and not after some random time.
There are also wss socket errors. Later I did some digging and there were some issues with FF and websockets connections. I temporarily set the flag of network.websocket.allowInsecureFromHTTPS and will test it out.
To make tl;dr so far:
Hardware acceleration ON = wss socket no connection to server errors, blank mp4 ect.
Hardware acceleration OFF = everything fine except that FF uses a lot of CPU on youtube ect.....
|
|
Reporter | |
Comment 11•2 years ago
|
||
I have another update. For tests I forced nVidia card (instead of default Intel) and HW on of course. So far no media issues.
Is FF compatible with nVidia Optimus (double GPUs) systems? It seems it can struggle on Intel, but work on nVidia. Still the weird thing is that even if it cannot work fully on Intel card, what does it have to do with broken wss socket connections.
|
|
Reporter | |
Comment 12•2 years ago
|
||
Ok I have the final verdict - after testing with nVidia and Intel GPU I can clearly say than Firefox is not compatible with Intel GPU, at least not with UHD 630 series.
nVidia makes no issues here, seems that hardware is broken in FF.
|
|
Reporter | |
Comment 13•2 years ago
|
||
Hardware acceleration I meant :)
|
|
||
Comment 14•2 years ago
|
||
The severity field is not set for this bug.
:jimm, could you have a look please?
For more information, please visit BugBot documentation.
|
||
Updated•2 years ago
|
|
|
||
Comment 15•2 years ago
|
||
The severity field is not set for this bug.
:bhood, could you have a look please?
For more information, please visit BugBot documentation.
|
||
Comment 16•2 years ago
|
||
Tim, can you please toss Priority/Severity settings on this report?
|
|
||
Updated•2 years ago
|
|
|
Reporter | |
Comment 17•1 year ago
|
||
Guys, I have a newer update.
Using FF 133 now - the problem with movies is back. To be sure I disabled all addons, deleted prefs.js for about:config to reset and use only ublock which I disable and enable.
I opened Twitter and wanted to play a video. Of course it failed. I need o restart FF and it works OK.
I tried to disable websockets, ect and nothing. No effect.
So far such issue never occured in any browser I tried, than FF. Are these logs helpful?
Content-Security-Policy: Ignoring ''unsafe-inline'' in script-src: 'nonce-source' or 'hash-source' specified 1867375935038668884
Loading failed for element 'script' with source 'https://abs.twimg.com/responsive-web/client-web/vendor.2e1dddca.js'. 1867375935038668884:325:401
[GSI_LOGGER]: Your client application uses one of the Google One Tap prompt UI status methods that may stop functioning when FedCM becomes mandatory. Refer to the migration guide to update your code accordingly and opt-in to FedCM to test your changes. Learn more: https://developers.google.com/identity/gsi/web/guides/fedcm-migration?s=dc#display_moment and https://developers.google.com/identity/gsi/web/guides/fedcm -migration?s=dc#skipped_moment client:172:419
Blocked request to cross-origin resource: 'Same Origin Policy' does not allow loading remote resources from 'https://api.x.com/1.1/jot/client_event.json' ” (CORS request failed). Status code: (null).
3
Request to cross-origin resource blocked: 'Same Origin Policy' does not allow loading remote resources from 'https://accounts.google.com/gsi/log?client_id=49625052041-kgt0hghf445lmcmhijv46b715m2mpbct.apps.googleusercontent.com&as=JOkF%2Fiaz0sV1R3WT2XGUiA&event =onetap.card.prompt.cooldown.2” (CORS request failed). Status code: (null).
Feature Policy: Skipping unsupported feature name ("identity-credentials-get"). client:270:304
Feature Policy: Skipping unsupported function name ('identity-credentials-get'). client:271:286
XHRGET
https://api.x.com/graphql/ZQPE2AJgdo3ydgxNW2I7Fg/ExploreSidebar?variables={}&features={"profile_label_improvements_pcf_label_in_post_enabled":false,"rweb_tipjar_consumpti on_enabled":true,"responsive_web_graphql_exclude_directive_enabled":true,"verified_phone_label_enabled":false,"creator_subscriptions_tweet_preview_api_enabled":true,"resp onsive_web_graphql_timeline_navigation_enabled":true,"responsive_web_graphql_skip_user_profile_image_extensions_enabled":false,"premium_content_api_read_enabled":false,"communities_ web_enable_tweet_community_results_fetch":true,"c9s_tweet_anatomy_moderator_badge_enabled":true,"responsive_web_grok_analyze_button_fetch_trends_enabled":false,"articles_preview_ena error":true,"responsive_web_edit_tweet_api_enabled":true,"graphql_is_translatable_rweb_tweet_is_translatable_enabled":true,"view_counts_everywhere_api_enabled":true,"longform_notetwe ets_consumption_enabled":true,"responsive_web_twitter_article_tweet_consumption_enabled":true,"tweet_awards_web_tipping_enabled":false,"creator_subscriptions_quote_tweet_preview_ena error":false,"freedom_of_speech_not_reach_fetch_enabled":true,"standardized_nudges_misinfo":true,"tweet_with_visibility_results_prefer_gql_limited_actions_policy_enabled":true,"r web_video_timestamps_enabled":true,"longform_notetweets_rich_text_read_enabled":true,"longform_notetweets_inline_media_enabled":true,"responsive_web_enhance_cards_enabled":false}
[HTTP/2 404 142ms]
Content-Security-Policy Warnings 5
Cookie Warnings 2
Blocked request to resource of another origin: 'Same Origin Policy' does not allow loading remote resources from 'https://api.x.com/1.1/jot/client_event.json' ” (CORS request failed). Status code: (null).
2
Request to cross-origin resource blocked: 'Same Origin Policy' does not allow loading remote resources from 'https://api.x.com/1.1/jot/client_event .json" (CORS request failed). Status code: (null).
Request to cross-origin resource blocked: 'Same Origin Policy' does not allow loading remote resources from 'https://api.x.com/1.1/jot/' ces/p2” (CORS request failed). Status code: (null).
Request to cross-origin resource blocked: 'Same Origin Policy' does not allow loading remote resources from 'https://api.x.com/1.1/jot/client_event.json' (CORS request failed) . Status code: (null).
Request to cross-origin resource blocked: 'Same Origin Policy' does not allow loading remote resources from 'https://api.x.com/1.1/jot/error_log.json' (CORS request failed ). Status code: (null).
Request to cross-origin resource blocked: 'Same Origin Policy' does not allow loading remote resources from 'https://api.x.com/1.1/jot/client_event.json' (Failed request CORS). Status code: (null).
Description
•