<iframe> Embedded youtube frames crash with fission enabled
Categories
(Core :: Audio/Video: Playback, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox76 | --- | fixed |
People
(Reporter: wtds.trabalho, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
- Open: https://www.amd.com/en/products/ryzen-threadripper
- Crash inside the iframes
- about:framecrashed?e=framecrashed&u=about%3Ablank&c=UTF-8&f=regular&d=%20
Actual results:
- Frame with errors
Expected results:
No errors,
Thanks!
Reporter | ||
Comment 1•5 years ago
|
||
From console.
Warnings:
17:52:48.787 Ignoring unsupported entryTypes: paint. ryzen-threadripper:4:2300
17:52:48.787 No valid entryTypes; aborting registration. ryzen-threadripper:4:2300
17:52:48.787 Ignoring unsupported entryTypes: largest-contentful-paint. ryzen-threadripper:4:2334
17:52:48.787 No valid entryTypes; aborting registration. ryzen-threadripper:4:2334
17:52:48.835
The resource at “<URL>” was blocked because content blocking is enabled. 10
17:52:48.920 This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. ryzen-threadripper
17:52:49.079
Request to access cookie or storage on “<URL>” was blocked because we are blocking all third-party storage access requests and content blocking is enabled. 12
17:52:49.079 Request to access cookie or storage on “https://www.youtube.com/embed/iBkC-8T85So?autoplay=0&start=0&rel=0” was blocked because we are blocking all third-party storage access requests and content blocking is enabled.
17:52:49.079 Request to access cookie or storage on “https://www.youtube.com/embed/ll2cipUZWPQ?autoplay=0&start=0&rel=0” was blocked because we are blocking all third-party storage access requests and content blocking is enabled.
17:52:49.079 Request to access cookie or storage on “https://www.youtube.com/embed/7SkXyJTgVlg?autoplay=0&start=0&rel=0” was blocked because we are blocking all third-party storage access requests and content blocking is enabled.
17:52:49.334 Request to access cookie or storage on “https://www.youtube.com/embed/iBkC-8T85So?autoplay=0&start=0&rel=0” was blocked because we are blocking all third-party storage access requests and content blocking is enabled.
17:52:49.335 Request to access cookie or storage on “https://www.youtube.com/embed/7SkXyJTgVlg?autoplay=0&start=0&rel=0” was blocked because we are blocking all third-party storage access requests and content blocking is enabled.
17:52:49.335 Request to access cookie or storage on “https://www.youtube.com/embed/ll2cipUZWPQ?autoplay=0&start=0&rel=0” was blocked because we are blocking all third-party storage access requests and content blocking is enabled.
17:52:49.505 Request to access cookie or storage on “https://www.google.com/pagead/conversion_async.js” was blocked because we are blocking all third-party storage access requests and content blocking is enabled.
17:52:49.553 Request to access cookie or storage on “https://www.google.com/pagead/conversion_async.js” was blocked because we are blocking all third-party storage access requests and content blocking is enabled.
17:52:49.632 Request to access cookie or storage on “https://www.youtube.com/iframe_api” was blocked because we are blocking all third-party storage access requests and content blocking is enabled.
17:52:49.911 Request to access cookie or storage on “https://www.youtube.com/embed/iBkC-8T85So?autoplay=0&start=0&rel=0” was blocked because we are blocking all third-party storage access requests and content blocking is enabled.
17:52:49.911 Request to access cookie or storage on “https://www.youtube.com/embed/7SkXyJTgVlg?autoplay=0&start=0&rel=0” was blocked because we are blocking all third-party storage access requests and content blocking is enabled.
17:52:49.911 Request to access cookie or storage on “https://www.youtube.com/embed/ll2cipUZWPQ?autoplay=0&start=0&rel=0” was blocked because we are blocking all third-party storage access requests and content blocking is enabled.
Reporter | ||
Comment 2•5 years ago
|
||
From console.
From Errors:
17:52:49.094 downloadable font: incorrect file size in WOFF header (font-family: "Klavika Light Condensed" style:normal weight:300 stretch:100 src index:1) source: https://www.amd.com/themes/custom/amd/fonts/Klavika-LightCondensed.woff
17:52:49.094 downloadable font: rejected by sanitizer (font-family: "Klavika Light Condensed" style:normal weight:300 stretch:100 src index:1) source: https://www.amd.com/themes/custom/amd/fonts/Klavika-LightCondensed.woff
DOMWindow:
17:52:50.764 Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://www.youtube.com’) does not match the recipient window’s origin (‘https://www.amd.com’). 10 ryzen-threadripper
17:52:51.266 Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://www.youtube.com’) does not match the recipient window’s origin (‘null’).
Thanks
Reporter | ||
Comment 3•5 years ago
|
||
Problem still occurring without addons but the site opens normal in Private mode.
In private mode I can print but the frame doesn't appears on printscreen.
Thanks!
Reporter | ||
Comment 4•5 years ago
|
||
Private mode. "Take a screenshot" tools can't print the video frames.
Thanks!
Comment 5•5 years ago
|
||
I can't see this issue of yours on the webpage you linked in the description on neither of the Firefox versions on Windows 10 or on Ubuntu 18. I haven't noticed any kind of areas with missing or misrendered content on both the private and non-private modes.
Are there some kind of preferences you modified or user data you have?
Would you please attempt it in a newly created profile as well? if it still occurs in a newly created profile, then a copy of the about:support page might help since it may be related to the hardware or else.
Thank you for your contribution!
Comment 6•5 years ago
|
||
Reminder.
Reporter | ||
Comment 7•5 years ago
|
||
Reporter | ||
Comment 8•5 years ago
|
||
I can't reset the profile for now.
But, it's my config: Attached... daniel.bodea@softvision.ro
Comment 9•5 years ago
|
||
OK. It did reproduce in the latest Nightly (the profile from which you provided the about:support information), right?
Firstly, you don't have to lose the current profile if you create a new one for testing. You can just reopen the old profile afterward.
Otherwise, it should suffice to try to reproduce it in safe mode. Can you do that?
Comment 10•5 years ago
|
||
Setting component to (Core) Layout. If incorrect, please set a more appropriate one rather than reverting the change. Thank you!
Comment 11•5 years ago
|
||
I can't see this, but I assume this is with fission enabled or something? Those are youtube embeds.
Comment 12•5 years ago
•
|
||
His prefs has fission.autostart: true
so it seems so?
Updated•5 years ago
|
Comment 13•5 years ago
|
||
I looked at the crash reports in the about:support, and they had the signature [@ mozilla::dom::MediaSessionController::UpdateActiveMediaSessionContextId ], which led me to bug 1623950. The steps to reproduce are similar in that bug, so I'm going to dupe this over. Feel free to reopen if you are still seeing crashes with an updated Nightly.
Updated•5 years ago
|
Updated•5 years ago
|
Description
•