Closed Bug 1735595 Opened 3 years ago Closed 3 years ago

Waiting for static.xx.fbcdn.net and Facebook Images Not Loading

Categories

(Core :: Networking, defect, P1)

Product:
Core
Component:
Networking
Version:
Firefox 93
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
98 Branch
Tracking Flags:
Tracking Status
firefox93 --- wontfix
firefox94 --- wontfix
firefox95 --- wontfix
firefox96 --- wontfix
firefox97 --- fixed
firefox98 --- fixed

People

(Reporter: Marc_Ragusa, Assigned: valentin, NeedInfo)

References

Details

(Whiteboard: [necko-triaged])

Attachments

(23 files)

Screenshot
431.72 KB, image/png
Details
Firefox 2021-10-18 13.42 profile.json.gz
5.03 MB, application/x-gzip
Details
Network requests
89.21 KB, image/png
Details
log.txt-main.14648.moz_log.zip
825.36 KB, application/x-zip-compressed
Details
log.txt-main.13500.moz_log.zip
749.53 KB, application/x-zip-compressed
Details
Firefox Facebook Images Not Loading.jpg
141.02 KB, image/jpeg
Details
Firefox Facebook Images Not Loading 2.jpg
106.24 KB, image/jpeg
Details
static.xx.fbcdn.net.txt-main.12596.moz_log.zip
804.58 KB, application/x-zip-compressed
Details
Facebook Reload Image.txt-main.6608.moz_log
4.28 MB, application/octet-stream
Details
Waiting for static.xx.fbcdn.net.txt-main.17040.moz_log
4.12 MB, application/octet-stream
Details
2 Waiting for static.xx.fbcdn.net.txt-main.19032.moz_log
4.41 MB, application/octet-stream
Details
Image Time outs.txt-main.14092.zip
9.79 MB, application/x-zip-compressed
Details
Intrepid Firefox 2021-11-14 15.35 profile.json.gz
3.93 MB, application/x-gzip
Details
11-16-21.txt-main.3612.moz_log.zip
1.18 MB, application/x-zip-compressed
Details
Images not loading.txt-main.18872.zip
6.53 MB, application/x-zip-compressed
Details
Waiting for static.xx.fbcdn.net and Facebook Images Not Loading
1.98 MB, application/x-zip-compressed
Details
Waiting for scontent.fmia1-1.fna.fbcdn.net
5.76 MB, application/x-zip-compressed
Details
12-9-21 Facebook Image not loading
1.85 MB, application/x-zip-compressed
Details
Missing icons example and console errors
140.73 KB, image/png
Details
Spinning Circle.jpg
145.19 KB, image/jpeg
Details
Default App - Google Chrome.png
4.43 KB, image/png
Details
Bug 1735595 - Do not cache 408 responses r=#necko
48 bytes, text/x-phabricator-request
RyanVM
: approval-mozilla-beta+
Details | Review
still not fix since version 94, wth is this problem
264.94 KB, image/jpeg
Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:93.0) Gecko/20100101 Firefox/93.0

Steps to reproduce:

Go to www.Facebook.com

Actual results:

Facebook says "waiting for static.xx.fbcdn.net" and Facebook images are not loading.

See: https://www.reddit.com/r/firefox/comments/pbkaro/waiting_for_staticxxfbcdnnet_message_when/

Expected results:

The page should load normally, like in Chrome.

Correction: Firefox says "waiting for static.xx.fbcdn.net" and Facebook images don't load.

Hi Interpid,
Looking at the reddit thread and seems like you already tried this out with addons disabled but it didn't fix it.
Do you have any strict Anti Tracking options enabled?
Could you please also try to delete the Cookies and Site Data for Facebook and see if it will load fine afterward? Please note that this will log you out from Facebook.

Meanwhile, I am moving this over to Networking component so developers from there can also check this out.
Thank you for this report!

Component: Untriaged → Networking
Flags: needinfo?(Marc)
Product: Firefox → Core

Many people are having the same issue. Firefox is not loading some images on the Facebook news feed and is showing "waiting for static.xx.fbcdn.net" These issues do not happen with Chrome. This is definitely a FF bug.
More Reports of the issue here: https://www.reddit.com/r/firefox/comments/q6jte3/facebook_is_having_a_hard_time_loading_correctly/
And Here: https://www.reddit.com/r/firefox/comments/pbkaro/waiting_for_staticxxfbcdnnet_message_when/

Flags: needinfo?(Marc)

Meanwhile, I am moving this over to Networking component so developers from there can also check this out.
Thank you for this report

Do you have any strict Anti Tracking options enabled? NO
Could you please also try to delete the Cookies and Site Data for Facebook and see if it will load fine afterward? YES, first thing I tried. :-)

I'm Experiencing the EXACT same issue ; Firefox 93 (64bit) client.
Ctrl+F5 seem to temporarily fix this, until it happens next time.

Severity: -- → S2
Summary: Waiting for static.xx.fbcdn.net → Waiting for static.xx.fbcdn.net and Facebook Images Not Loading

Can either Interpid or Sagi please record a performance profile using the Firefox Profiler? Here are instructions for enabling the Firefox Profiler:

https://profiler.firefox.com/

Please change these profiler settings, looking at a similar Bug 1700968 Comment 12:

  • Click the profiler toolbar button's down arrow.
  • Change Settings to "Custom".
  • Click "Edit Settings".
  • Then search for and check the "DOM Worker" and "IPC Messages" checkboxes.

Please don't forget to upload the performance profile and share it here. Thanks!

Flags: needinfo?(jliebert90)
Flags: needinfo?(denebsystem)
Attached image Screenshot —

I might've also just encountered this on the latest Beta 94.0b7 (64-bit) on MacOS 10.15. It was only once tho and I am yet to find some reliable steps to reproduce. Confirming for Beta 94, but it is intermittent and not reliably reproducible yet, at least not on my side.
Downgrading severity to S3 since it is intermittent and needs more investigations to set up correctly the affected versions.
If any of you could pinpoint to observed 100% reproducibility steps, please let us know.
Please note that in my case, I got: "Waiting for scontent.fclj2-fna.fbcdn.net..."

Severity: S2 → S3
Status: UNCONFIRMED → NEW
status-firefox93: --- → ?
status-firefox94: --- → affected
status-firefox95: --- → ?
Ever confirmed: true

Meanwhile, Sagi just sent me via an email the recorded profile. Attaching it here for further investigations. Thanks!
Edit: uploaded the profile here: https://share.firefox.dev/3G7UMf5

Flags: needinfo?(denebsystem)

I hereby attach my record during issue reproduction.
Please let me know if there are any further steps to be done in order to provide better tracking.
I also emailed directly Timea Cernea with a different record, but more than one the better.

https://share.firefox.dev/3p9Kd4Y

Thank again Sagi! As I said above, if you could also lookout for a reproducibility pattern or just let us know that this is reproducible at all times, that would be great. Also, I hope you're already gone through all the troubleshooting steps, such as: Safe Mode, New Profile, Clear Cookies&Cache, etc.
Hi :jstutte, could you please redirect this NI? to someone that can analyse the performance profile and help this ticket move further?

Flags: needinfo?(jstutte)

Sure thing.
I've tried all of the things you mentioned. It is also worth mentioning that I'm after a fresh Install of the whole OS (Win10). The issue shows up pretty frequently so it's hard to say what is causing this. For now I tried to disable hardware acceleration in browser to see if this helps in any way.

Important Update.
I found a way to reliably replicate the bug.
It's also happening at certain other sites. For example, you can cause the malfunction by doing the following:

  1. Go to https://www.lifeextension.com
  2. In the search box at the top, type something and hit the Enter key.
    Result: Firefox malfunction - page never loads.

I have tested this on 3 different PCs and also in troubleshooting mode.
The page works fine in Chrome.

Severity: S3 → S2

I just spoke with two colleagues who are reporting the same issues - Firefox is not properly loading certain pages but they work fine in Chrome. This is a serous S2 Bug. We're having to move to Chrome. Thank You!

Attached image Network requests —

Thank you for the report.
For some reason it seems the server is not responding to some requests.
The connection is still working, as some later requests to the same domain are completed successfully.

Would you be able to capture some network logs when this bug happens?
https://firefox-source-docs.mozilla.org/networking/http/logging.html

Flags: needinfo?(Marc)

It seems to be a duplicate of bug 1732628.

See Also: → 1732628

The issue happens sporadically. I've captured a log for https://www.lifeextension.com when using the product search on the page.

Flags: needinfo?(Marc)

Facebook: Waiting for static.xx.fbcdn.net

(In reply to Valentin Gosu [:valentin] (he/him) from comment #15)

I Attached a log for facebook. Thanks.

The log shows that static.xx.fbcdn.net returns some 408 responses.

  HTTP/3 408 Request Timeout
  content-type: text/html; charset=utf-8
  content-length: 2959
  priority: u=3,i
  date: Wed, 27 Oct 2021 02:04:35 GMT

The reason is not clear. Maybe Dragana has an idea?

Flags: needinfo?(dd.mozilla)

I do not see anything strange on our side. I will see to get some input from facebook.

Flags: needinfo?(dd.mozilla)
Priority: -- → P1
Whiteboard: [necko-triaged]

I strongly disagree. I can have Firefox and chrome open side-by-side. Facebook images will load properly in Chrome and not in Firefox.
Same for other sites such as https://www.lifeextension.com where search hangs on Firefox but not in Chrome.
Restarting Firefox often fixes the issue until next time. This is occuring on different PCs as well.
Firefox has a 3.5% market share. It's obvious that websites are being coded to work with Chromium. I guess it's time to move on. Thanks for the memories.

(In reply to Intrepid from comment #23)

I strongly disagree. I can have Firefox and chrome open side-by-side. Facebook images will load properly in Chrome and not in Firefox.
Same for other sites such as https://www.lifeextension.com where search hangs on Firefox but not in Chrome.
Restarting Firefox often fixes the issue until next time. This is occuring on different PCs as well.
Firefox has a 3.5% market share. It's obvious that websites are being coded to work with Chromium. I guess it's time to move on. Thanks for the memories.

No need to get offended... :) This is either (and most probably) a Firefox issue or the website is designed to "discriminate" some browsers. Anyway, let's hope Firefox developers will sort this out quickly as it's a bit pain in the back, but personally just for that I won't switch from my favorite browser.

Can someone try to change the following prefs and see if the problem still exist:
network.http.http3.default-max-stream-blocked set it to 0
network.http.http3.default-qpack-table-size set it to 0

Thank you!

(In reply to Intrepid from comment #17)

Created attachment 9247647 [details]
log.txt-main.14648.moz_log.zip

The issue happens sporadically. I've captured a log for https://www.lifeextension.com when using the product search on the page.

This is a different issue. I need to understand more.

I see that something is canceling a HTTP request but I do not know what.
Is there anything in the console? what does DevTool show?

Thank you!

Flags: needinfo?(Marc)

(In reply to Dragana Damjanovic [:dragana] from comment #27)

Can someone try to change the following prefs and see if the problem still exist:
network.http.http3.default-max-stream-blocked set it to 0
network.http.http3.default-qpack-table-size set it to 0

Thank you!

Changed it, will let you know if I still get the same problem after that. It will take some time tho, as this is not a constant issue.

(In reply to Dragana Damjanovic [:dragana] from comment #27)

Can someone try to change the following prefs and see if the problem still exist:
network.http.http3.default-max-stream-blocked set it to 0
network.http.http3.default-qpack-table-size set it to 0

Thank you!

I will test today and let you know. Thanks.
(In reply to Dragana Damjanovic [:dragana] from comment #27)

Can someone try to change the following prefs and see if the problem still exist:
network.http.http3.default-max-stream-blocked set it to 0
network.http.http3.default-qpack-table-size set it to 0

Thank you!

I will test today and let you know. Thanks.

Flags: needinfo?(Marc)

(In reply to Dragana Damjanovic [:dragana] from comment #27)

Can someone try to change the following prefs and see if the problem still exist:
network.http.http3.default-max-stream-blocked set it to 0
network.http.http3.default-qpack-table-size set it to 0

Thank you!

Unfortunately, it started happening again after making both pref changes.
Uploaded screenshot.

May I ask you to make another log with:

timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

Thank you!

(In reply to Dragana Damjanovic [:dragana] from comment #34)

May I ask you to make another log with:

timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

Thank you!

I know how to make a log while the bug occurs, but I don 't know what to do with this: timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5
Please provide instructions. Thanks.

(In reply to Intrepid from comment #35)

(In reply to Dragana Damjanovic [:dragana] from comment #34)

May I ask you to make another log with:

timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

Thank you!

I know how to make a log while the bug occurs, but I don 't know what to do with this: timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5
Please provide instructions. Thanks.

Please take a look at https://firefox-source-docs.mozilla.org/networking/http/logging.html.
Just set the environment variable MOZ_LOG to timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5. Thanks.

(In reply to Kershaw Chang [:kershaw] from comment #36)

(In reply to Intrepid from comment #35)

(In reply to Dragana Damjanovic [:dragana] from comment #34)

Please take a look at https://firefox-source-docs.mozilla.org/networking/http/logging.html.
Just set the environment variable MOZ_LOG to timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5. Thanks.

I need a way to turn on logging while Firefox is running. If I turn it on the way you suggest, it could take hours or even a day for the issue to appear. The log file would be massive.

(In reply to Intrepid from comment #37)

(In reply to Kershaw Chang [:kershaw] from comment #36)

(In reply to Intrepid from comment #35)

(In reply to Dragana Damjanovic [:dragana] from comment #34)

Please take a look at https://firefox-source-docs.mozilla.org/networking/http/logging.html.
Just set the environment variable MOZ_LOG to timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5. Thanks.

I need a way to turn on logging while Firefox is running. If I turn it on the way you suggest, it could take hours or even a day for the issue to appear. The log file would be massive.

(In reply to Kershaw Chang [:kershaw] from comment #36)

(In reply to Intrepid from comment #35)

(In reply to Dragana Damjanovic [:dragana] from comment #34)

May I ask you to make another log with:

timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

Thank you!

I know how to make a log while the bug occurs, but I don 't know what to do with this: timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5
Please provide instructions. Thanks.

Please take a look at https://firefox-source-docs.mozilla.org/networking/http/logging.html.
Just set the environment variable MOZ_LOG to timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5. Thanks.

(In reply to Kershaw Chang [:kershaw] from comment #36)

(In reply to Intrepid from comment #35)

(In reply to Dragana Damjanovic [:dragana] from comment #34)

May I ask you to make another log with:

timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

Thank you!

I know how to make a log while the bug occurs, but I don 't know what to do with this: timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5
Please provide instructions. Thanks.

Please take a look at https://firefox-source-docs.mozilla.org/networking/http/logging.html.
Just set the environment variable MOZ_LOG to timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5. Thanks.

Never mind. I see that you can enter this in about:networking#logging - Current Log Modules
timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5
I will log the problem when it appears again and post. Thanks.

(there is enough analysis ongoing without my nag here, it seems)

Flags: needinfo?(jstutte)

(In reply to Kershaw Chang [:kershaw] from comment #36)

(In reply to Intrepid from comment #35)

(In reply to Dragana Damjanovic [:dragana] from comment #34)

May I ask you to make another log with:

timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

Thank you!

I know how to make a log while the bug occurs, but I don 't know what to do with this: timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5
Please provide instructions. Thanks.

Please take a look at https://firefox-source-docs.mozilla.org/networking/http/logging.html.
Just set the environment variable MOZ_LOG to timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5. Thanks.

OK, I uploaded the log file: static.xx.fbcdn.net.txt-main.12596.moz_log.zip
Firefox: Waiting for static.xx.fbcdn.net
Then timeout after several minutes. I tried again and it loaded. All logged.
Thanks!

Facebook: Waiting for static.xx.fbcdn.net

I have the same problem, using the latest version of Firefox (94.0.1)
With previous version i've had this problem too and usually you have to restart firefox to fix it (temporarily) , you can wait for firefox to time out but restarting is quicker.

(In reply to Dragana Damjanovic [:dragana] from comment #34)

May I ask you to make another log with:

timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

Thank you!

I added two logs:

static.xx.fbcdn.net.txt-main.12596.moz_log.zip
and
Facebook Reload Image.txt-main.6608.moz_log

Thanks.

Log while right clicking on an unloaded image and selecting "reload image" in Firefox.
Facebook Reload Image.txt-main.6608.moz_log

Another Log for Facebook: Waiting for static.xx.fbcdn.net
Logged using: timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

Another log for Waiting for static.xx.fbcdn.net when loading a Facebook page.
Log used: timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

(In reply to Dragana Damjanovic [:dragana] from comment #34)

May I ask you to make another log with:

timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

Thank you!

More Logs uploaded.

Firefox stalling on Facebook Images. Images not loading in Firefox.
Logged using: timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

(In reply to Timea Cernea [:tbabos] from comment #7)

Can either Interpid or Sagi please record a performance profile using the Firefox Profiler? Here are instructions for enabling the Firefox Profiler:

https://profiler.firefox.com/

Please change these profiler settings, looking at a similar Bug 1700968 Comment 12:

  • Click the profiler toolbar button's down arrow.
  • Change Settings to "Custom".
  • Click "Edit Settings".
  • Then search for and check the "DOM Worker" and "IPC Messages" checkboxes.

Please don't forget to upload the performance profile and share it here. Thanks!

More Logs Added. Thank You.

I've been having this same issue for at least several months.

My parents have the same issue also for a several months. Firefox on Android looks like have the same issue.

RE: Firefox not loading Facebook Images
Firefox Profile with "DOM Worker" and "IPC Messages"

(In reply to Timea Cernea [:tbabos] from comment #7)

Can either Interpid or Sagi please record a performance profile using the Firefox Profiler? Here are instructions for enabling the Firefox Profiler:

https://profiler.firefox.com/

Please change these profiler settings, looking at a similar Bug 1700968 Comment 12:

  • Click the profiler toolbar button's down arrow.
  • Change Settings to "Custom".
  • Click "Edit Settings".
  • Then search for and check the "DOM Worker" and "IPC Messages" checkboxes.

Please don't forget to upload the performance profile and share it here. Thanks!

Profile Uploaded.

(In reply to Dragana Damjanovic [:dragana] from comment #34)

May I ask you to make another log with:

timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

Thank you!

Added yet another log --- Facebook page will not load in Firefox: Waiting for static.xx.fbcdn.net
Loads fine in Chrome at the exact same time as the timeout in Firefox...
Logged using: timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

Added yet another log --- Facebook page will not load in Firefox: Waiting for static.xx.fbcdn.net
Loads fine in Chrome at the exact same time as the timeout in Firefox...
Logged using: timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

(In reply to Timea Cernea [:tbabos] from comment #2)

Hi Interpid,
Looking at the reddit thread and seems like you already tried this out with addons disabled but it didn't fix it.
Do you have any strict Anti Tracking options enabled?
Could you please also try to delete the Cookies and Site Data for Facebook and see if it will load fine afterward? Please note that this will log you out from Facebook.

Meanwhile, I am moving this over to Networking component so developers from there can also check this out.
Thank you for this report!

Added another log.
Firefox stalling on Facebook Images. Images not loading in Firefox.

Firefox stalling on Facebook Images. Images not loading in Firefox.

Same issue here, images not loading, sometimes they load, but then you start browsing and it suddenly dies. Been like this for months now, honestly thinking of switching after over a decade of usage.

Same issue here: restarting Firefox fixes the issue. Very annoying bug.

I've been having this problem for months as well. Am trying the below http3 settings:

network.http.http3.default-max-stream-blocked set it to 0
network.http.http3.default-qpack-table-size set it to 0

(In reply to Jeff Wasilko from comment #60)

I've been having this problem for months as well. Am trying the below http3 settings:

network.http.http3.default-max-stream-blocked set it to 0
network.http.http3.default-qpack-table-size set it to 0

I already tried this (see Comment 27 above) and it didn't help.

I've also noticed that toggling "Work Offline" can sometimes help restore image loading.

The http3 settings do seem to help, but I don't have a way to quantify. Firefox has been working with Facebook for more than 2 hours....

(In reply to Jeff Wasilko from comment #63)

The http3 settings do seem to help, but I don't have a way to quantify. Firefox has been working with Facebook for more than 2 hours....

In my experience, it takes 2 days to test not 2 hours as it's sporadic.

I must be special as it was breaking for me multiple times a day. I'm still going in the same session.... :-)

Same problem, varying degrees of severity, for months now--regardless of version. This seems to only affect FF based browsers. I had better results with the ESR until the last minor patch--now ESR is doing it too.
Doing a full refresh temporarily fixes it, but that should not be necessary on a daily basis.
Using OpenSUSE Tumbleweed, with FF 94.0

@drag(In reply to Dragana Damjanovic [:dragana] from comment #27)

Can someone try to change the following prefs and see if the problem still exist:
network.http.http3.default-max-stream-blocked set it to 0
network.http.http3.default-qpack-table-size set it to 0

Thank you!

I've been running with these two prefs set to 0 for about 24 hours now, and it's made a huge difference. I haven't had to restart Firefox at all, and I'm still able to scroll Facebook (lots and lots) and load images.

At least for me, this is a 100% resolution.

(In reply to Dragana Damjanovic [:dragana] from comment #34)

May I ask you to make another log with:

timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

Thank you!

dragana, What is the status of repairing this bug? Thank You.

(In reply to Jeff Wasilko from comment #67)

@drag(In reply to Dragana Damjanovic [:dragana] from comment #27)

Can someone try to change the following prefs and see if the problem still exist:
network.http.http3.default-max-stream-blocked set it to 0
network.http.http3.default-qpack-table-size set it to 0

Thank you!

I've been running with these two prefs set to 0 for about 24 hours now, and it's made a huge difference. I haven't had to restart Firefox at all, and I'm still able to scroll Facebook (lots and lots) and load images.

At least for me, this is a 100% resolution.

At first look, this does seem to be an effective work-around. Two questions:
Is there a way to apply this to Android?
What effect does this have on HTML3?

(In reply to Dragana Damjanovic [:dragana] from comment #27)

Can someone try to change the following prefs and see if the problem still exist:
network.http.http3.default-max-stream-blocked set it to 0
network.http.http3.default-qpack-table-size set it to 0

Thank you!

I tried these changes earlier this month and still had issues. There was some improvement, but it still happened. See Uploaded screenshots:
https://bug1735595.bmoattachments.org/attachment.cgi?id=9249334
https://bug1735595.bmoattachments.org/attachment.cgi?id=9249338

I can confirm this is happening on several computers running both Windows 10 and Linux Mint. Happening on all of them. Also if I right click on a broken image and choose "display image in another tab" it loads the image in the new tab correctly so it's not a broken image on FB. Also this is not happening in Chrome.

Walter - could you try the about:config settings referenced in #27 ?

The http3 settings seemed to immediately fix the issue for me.

@Devs Thank you for your work on this bug. Are there any additional logs or testing that we could help with?

(In reply to Timea Cernea [:tbabos] from comment #2)

Hi Interpid,
Looking at the reddit thread and seems like you already tried this out with addons disabled but it didn't fix it.
Do you have any strict Anti Tracking options enabled?
Could you please also try to delete the Cookies and Site Data for Facebook and see if it will load fine afterward? Please note that this will log you out from Facebook.

Meanwhile, I am moving this over to Networking component so developers from there can also check this out.
Thank you for this report!

Timea Cernea, Any updates on fixing this issue? Thanks.

(In reply to Dragana Damjanovic [:dragana] from comment #27)

network.http.http3.default-max-stream-blocked set it to 0
network.http.http3.default-qpack-table-size set it to 0

this solves the problem for me.

I'm amending my prior comment about:

network.http.http3.default-max-stream-blocked set it to 0
network.http.http3.default-qpack-table-size set it to 0

It is NOT an effective work-around, it merely delays the problem.

Looking at the logs from comment 57:

2021-11-19 17:03:06.312000 UTC - [Parent 18872: Main Thread]: V/nsHttp nsHttpResponseHead::ParseCachedHead [this=27cdac0b0c0]
2021-11-19 17:03:06.312000 UTC - [Parent 18872: Cache2 I/O]: D/cache2 CacheFileMetadata::OnDataRead() [this=27cde1ab700, handle=27cd6dfe760, result=0x00000000]
2021-11-19 17:03:06.312000 UTC - [Parent 18872: Main Thread]: V/nsHttp nsHttpResponseHead::ParseVersion [version=HTTP/3 408 Request Timeout
content-type: text/html; charset=utf-8
content-length: 2959
priority: u=3,i
date: Fri, 19 Nov 2021 17:02:36 GMT
X-Firefox-Http3: h3
]

From what I can see there are a bunch cached 408 requests for the image requests.
Could you clear your cache (Ctrl-Shift-Delete | Clear everything for Cache) and try again?
If you can still reproduce this, please use
timestamp,rotate:200,nsHttp:5,neqo_transport::*:5,neqo_http3::*:5 to record new logs. Thanks!

Flags: needinfo?(Marc)

There's also a fair number of channels that are cancelled with 80540005 (NS_IMAGELIB_ERROR_FAILURE).

Waiting for static.xx.fbcdn.net and Facebook Images Not Loading
Log recorded after clearing cache and using:
timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5
as requested by: Valentin Gosu [:valentin]

Flags: needinfo?(Marc)

Waiting for scontent.fmia1-1.fna.fbcdn.net - Facebook images not loading
Logged 12-8-21 using:
timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

(In reply to Valentin Gosu [:valentin] (he/him) from comment #78)

Looking at the logs from comment 57:

2021-11-19 17:03:06.312000 UTC - [Parent 18872: Main Thread]: V/nsHttp nsHttpResponseHead::ParseCachedHead [this=27cdac0b0c0]
2021-11-19 17:03:06.312000 UTC - [Parent 18872: Cache2 I/O]: D/cache2 CacheFileMetadata::OnDataRead() [this=27cde1ab700, handle=27cd6dfe760, result=0x00000000]
2021-11-19 17:03:06.312000 UTC - [Parent 18872: Main Thread]: V/nsHttp nsHttpResponseHead::ParseVersion [version=HTTP/3 408 Request Timeout
content-type: text/html; charset=utf-8
content-length: 2959
priority: u=3,i
date: Fri, 19 Nov 2021 17:02:36 GMT
X-Firefox-Http3: h3
]

From what I can see there are a bunch cached 408 requests for the image requests.
Could you clear your cache (Ctrl-Shift-Delete | Clear everything for Cache) and try again?
If you can still reproduce this, please use
timestamp,rotate:200,nsHttp:5,neqo_transport::*:5,neqo_http3::*:5 to record new logs. Thanks!

Another Logged uploaded for review.
Waiting for scontent.fmia1-1.fna.fbcdn.net - Facebook images not loading
Logged 12-8-21 using:
timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

Logged using: timestamp,rotate:200,nsHttp:5,neqo_transport:::5,neqo_http3:::5

(In reply to Valentin Gosu [:valentin] (he/him) from comment #78)

Looking at the logs from comment 57:

2021-11-19 17:03:06.312000 UTC - [Parent 18872: Main Thread]: V/nsHttp nsHttpResponseHead::ParseCachedHead [this=27cdac0b0c0]
2021-11-19 17:03:06.312000 UTC - [Parent 18872: Cache2 I/O]: D/cache2 CacheFileMetadata::OnDataRead() [this=27cde1ab700, handle=27cd6dfe760, result=0x00000000]
2021-11-19 17:03:06.312000 UTC - [Parent 18872: Main Thread]: V/nsHttp nsHttpResponseHead::ParseVersion [version=HTTP/3 408 Request Timeout
content-type: text/html; charset=utf-8
content-length: 2959
priority: u=3,i
date: Fri, 19 Nov 2021 17:02:36 GMT
X-Firefox-Http3: h3
]

From what I can see there are a bunch cached 408 requests for the image requests.
Could you clear your cache (Ctrl-Shift-Delete | Clear everything for Cache) and try again?
If you can still reproduce this, please use
timestamp,rotate:200,nsHttp:5,neqo_transport::*:5,neqo_http3::*:5 to record new logs. Thanks!

When using this URL to open the Activity Log in Facebook, Firefox hangs and is slow to load the page. It works fine in Chrome. This Firefox bug is reproducible reliably.
https://www.facebook.com/100001314066613/allactivity?activity_history=true&category_key=ALL&manage_mode=false

Just chimining in to say I have been having the same issue for months. Images load in Chrome and FB mobile (same connection), but sometimes not in Firefox. I'm using Firefox 95.0 on OSX 12.0.1. Reloading the page with Cmd+Shift+R seems to solve the issue.

Please disregard my comment 84.
Anyway, is this bug getting fixed soon? Using Facebook with Firefox is now an annoyance...

I haven't found any potential cause for this in the logs.
Maybe Kershaw has better luck with this. Could you take a look?

@Intrepid, did you also clear the cache? Did it make any difference? How about reloading with Cmd+Shift+R/Ctrl+Shift+R?

Flags: needinfo?(jliebert90) → needinfo?(kershaw)

(In reply to Valentin Gosu [:valentin] (he/him) from comment #87)

I haven't found any potential cause for this in the logs.
Maybe Kershaw has better luck with this. Could you take a look?

@Intrepid, did you also clear the cache? Did it make any difference? How about reloading with Cmd+Shift+R/Ctrl+Shift+R?

Ctrl+Shift+R: Images load temporarily
Ctrl+Shift+Del - Clear Everything, Cache: Images load temporarily
Thanks.

Can't say if it's useful but, I have this unwanted behaviour since FB's DNS change (messup) event

This bug has been occurring for over 2 months now...

Hello! I was having exact same issue for past i guess 2 months (that feels right now when i think about it after seeing what you guys report). To throw my 2 cents for you i have prepared screenshot of example of missing images instance (turns out not only media people share, but also FB icons happens to be blocked). I have very limited knowledge about security and privacy when it comes to stuff reported in the console and FB scripts, so i have pixelated stuff that have any tiny chance of compromising it in my uneducated opinion - usually strings of characters or numbers that i have no idea of their functionality (sorry if thats redundant or makes it less useful afterwards - when unsure i try to follow "better safe than sorry" when i throw something into internet and i do want to help fixing that issue any way i can cause its really frustrating). The error codes and stuff is left untouched on the screen and might give more insight for someone. Hope it helps anyhow.

(In reply to Intrepid from comment #84)

(In reply to Valentin Gosu [:valentin] (he/him) from comment #78)
When using this URL to open the Activity Log in Facebook, Firefox hangs and is slow to load the page. It works fine in Chrome. This Firefox bug is reproducible reliably.
https://www.facebook.com/100001314066613/allactivity?activity_history=true&category_key=ALL&manage_mode=false

Just to add what i observe on my PC. WHen i open that link on Chrome (or just navigate to FB activity log) and click on "actions and other activity" (loose translation from polish) or "comments", it hangs permanently on Chrome aswell with greyed out screen and blue loading circle. So that part of FB malfunction might not be related to our missing images issue. For me even in Chrome activity log spits out lots of red errors in console after hanging like:

[Report Only] Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content >Security Policy directive: "script-src *.facebook.com *.fbcdn.net 'unsafe-inline' blob: data: 'self' *.whatsapp.com whatsapp.com *.whatsapp.net >whatsapp.net".

followed with:

Failed to load resource: the server responded with a status of 404 ()
scontent.xx.fbcdn.net/m1/v/t6/(...)

and:

Failed to load resource: net::ERR_FAILED
chrome-extension://invalid/:1

So i am not sure if you should connect activity log issue with missing images issue. That might take you into wrong track.

(In reply to Mariusz from comment #92)

(In reply to Intrepid from comment #84)

(In reply to Valentin Gosu [:valentin] (he/him) from comment #78)
When using this URL to open the Activity Log in Facebook, Firefox hangs and is slow to load the page. It works fine in Chrome. This Firefox bug is reproducible reliably.
https://www.facebook.com/100001314066613/allactivity?activity_history=true&category_key=ALL&manage_mode=false

Just to add what i observe on my PC. WHen i open that link on Chrome (or just navigate to FB activity log) and click on "actions and other activity" (loose translation from polish) or "comments", it hangs permanently on Chrome aswell with greyed out screen and blue loading circle. So that part of FB malfunction might not be related to our missing images issue. For me even in Chrome activity log spits out lots of red errors in console after hanging like:

[Report Only] Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content >Security Policy directive: "script-src *.facebook.com *.fbcdn.net 'unsafe-inline' blob: data: 'self' *.whatsapp.com whatsapp.com *.whatsapp.net >whatsapp.net".

followed with:

Failed to load resource: the server responded with a status of 404 ()
scontent.xx.fbcdn.net/m1/v/t6/(...)

and:

Failed to load resource: net::ERR_FAILED
chrome-extension://invalid/:1

So i am not sure if you should connect activity log issue with missing images issue. That might take you into wrong track.

I already retracted my comment about the activity log in comment #86. There is no way to delete or edit comments on here.

Facebook is becoming unusable with Firefox. This has been going on for over 2 months now.
https://www.reddit.com/r/firefox/comments/p85knm/facebook_images_randomly_fail_to_load/

Attached image Spinning Circle.jpg —

This is getting really old! Images not loading, comment infinite spinning circle...

I think I have this issue on (old) Reddit (missing sprites and header images on r/uBlock and r/Firefox). I'm pretty sure toggling browser.cache.disk.enable helps. Can anyone check this too?

(In reply to Valentin Gosu [:valentin] (he/him) [PTO until Jan 17th] from comment #87)

I haven't found any potential cause for this in the logs.
Maybe Kershaw has better luck with this. Could you take a look?

Sorry, I also can't find out the reason why we got so many 408 Request Timeout responses.

@Intrepid, not sure if we asked this before. Are you able to reproduce this with the latest nightly and with a clean profile?

Flags: needinfo?(kershaw)

(In reply to Kershaw Chang [:kershaw] from comment #97)
(In reply to gwarser from comment #96)

I think I have this issue on (old) Reddit (missing sprites and header images on r/uBlock and r/Firefox). I'm pretty sure toggling browser.cache.disk.enable helps. Can anyone check this too?

browser.cache.disk.enable set to FALSE and clearing the cache (Ctrl+Shift+Del, Everything, Cache) definitely fixes the issue. This appears to be related to the Firefox cache. Please fix the bug! Thanks.

(In reply to Intrepid from comment #98)

(In reply to Kershaw Chang [:kershaw] from comment #97)
(In reply to gwarser from comment #96)

I think I have this issue on (old) Reddit (missing sprites and header images on r/uBlock and r/Firefox). I'm pretty sure toggling browser.cache.disk.enable helps. Can anyone check this too?

browser.cache.disk.enable set to FALSE and clearing the cache (Ctrl+Shift+Del, Everything, Cache) definitely fixes the issue. This appears to be related to the Firefox cache. Please fix the bug! Thanks.

I can confirm this works. I have had this issue for almost 6 months and this worked. I was about to scrap FireFox for Edge. They need to fix the caching. I figured this would work, because clearing my cache manually was working previously, but that cache saves something that it shouldn't, because in less than 6 hours I would always be in the same situation with no images and elements not loading. Thanks for the info!

This bug is now 3 months old.

@(In reply to Intrepid from comment #100)

This bug is now 3 months old.

Hey, just created an account because of the reddit posts point me here. This issue has plagued me for months, and I've been a long time 10+ years Firefox user. I've enjoyed this thread and finally found a permanent solution that someone else already commented on. Hope this helps.

I was excited to see that Firefox 96.0 just came out, only to find that the Facebook experience is worse than before. Comments don't load, images are grayed out.

I have been following this thread for a few months, trying most of the suggested fixes, as others have said, I guess it is time to switch to Chrome?

With ff96 without modifiers the problem it's much rarest but still present.

I have the same issue for months, including the 96.0 version. I already tried to create a new fresh Firefox profile and disable the Enhanced Tracking Protection for the Facebook web site. Nothing helps.

It seems to be related to caching somehow, because even reloading the Facebook web page by F5 won't help, Ctrl+F5 helps only.

It may be a bug in HTTP3 implementation. I disabled it in about:config by setting: network.http.http3.enabled = false

Opening (the most relevant) discussions for public Facebook posts works again and I haven't had any stuck images for several hours. It is still too early to say whether it is a workaround or not, I'll report back in a week.

(In reply to Petr Vones from comment #105)

It may be a bug in HTTP3 implementation. I disabled it in about:config by setting: network.http.http3.enabled = false

Opening (the most relevant) discussions for public Facebook posts works again and I haven't had any stuck images for several hours. It is still too early to say whether it is a workaround or not, I'll report back in a week.

browser.cache.disk.enable set to FALSE and clearing the cache (Ctrl+Shift+Del, Everything, Cache) definitely fixes the issue. This appears to be related to the Firefox cache. Please fix the bug! Thanks.

Same issue for months. Don't want to use another browser if I can help it. FF is my favorite browser. Kindly fix.

(In reply to Intrepid from comment #106)

browser.cache.disk.enable set to FALSE and clearing the cache (Ctrl+Shift+Del, Everything, Cache) definitely fixes the issue. This appears to be

But I don't want to disable the browser cache, it makes everything slower. It seems that disabling the HTTP3 protocol resolves it, I haven't had any issues since that.

I updated to 96.0.1 as there is a HTTP3 fix (bug 1749957) and re-enabled the HTTP3. Unfortunately the issue has appeared again within ten minutes, so I'll continue with the testing when the HTTP3 is disabled.

It seems as there are more web sites than the Facebook having problems with the HTTP3 in Firefox
https://www.reddit.com/r/firefox/comments/s2utvv/psa_solution_for_firefox_not_working_right_now/

Facebook responds with 408 when a HTTP/3 connection has been idle for too
long. This is problematic since there are no caching headers added to the
response and it causes application errors if the response is loaded from
the cache.

Assignee: nobody → valentin.gosu
Status: NEW → ASSIGNED
Pushed by valentin.gosu@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/7ae5e8624dba
Do not cache 408 responses r=necko-reviewers,kershaw

https://hg.mozilla.org/mozilla-central/rev/7ae5e8624dba

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox98: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 98 Branch

So easy, lol! Thank you team <3

still doesn't work for me, is there something we have to update?

The update should hit Nightly with the next update. Please report back if you're still seeing the issue tomorrow.

(In reply to JC3 from comment #115)

still doesn't work for me, is there something we have to update?

The fix (which I have not tested yet) will not be available to the general public until Firefox 98 is released.
If you want it now, here is a link - but I honestly have NO IDEA what do download: https://hg.mozilla.org/mozilla-central/rev/7ae5e8624dba

The nightly can be downloaded here, https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly

I'm not running it until it's part of the normal update, I'm not a Alpha tester and don't need anymore issues

Comment on attachment 9259342 [details]
Bug 1735595 - Do not cache 408 responses r=#necko

Beta/Release Uplift Approval Request

  • User impact if declined: Facebook users using HTTP/3 might encounter stuck spinners.
    This is caused by Facebook closing the connection with a 408 response, and us caching that response.
    The problem only goes went after a force-refresh that bypasses the cache.
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): This change alters the caching behaviour for 408 responses to be similar to that of 425 and 429 responses, so we don't cache them.
    Even if the 408 responses from the server occur, they will not be cached, so a normal refresh will fix the application state.
  • String changes made/needed:
Attachment #9259342 - Flags: approval-mozilla-beta?

Comment on attachment 9259342 [details]
Bug 1735595 - Do not cache 408 responses r=#necko

Pretty annoying issue on a major site. Approved for 97.0b6. Also, I assume we'll want this on ESR also? And is this something we can/should have tests for?

Flags: needinfo?(valentin.gosu)
Attachment #9259342 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

Are their any timelines for 97 or 98 being released to the public? Great that it has been resolved but still broken in 96, according to the notes will not be fixed in 96.

Firefox 97 is scheduled for release on February 8.

Flags: qe-verify+
QA Whiteboard: [qa-triaged]

This bug still exists in Firefox 97.0b7, it went fine for a day or two and it just happened again.

(In reply to dubbeldrank from comment #124)

This bug still exists in Firefox 97.0b7, it went fine for a day or two and it just happened again.

Did it go away after a refresh?
If not, record some HTTP logs for us https://firefox-source-docs.mozilla.org/networking/http/logging.html
Thanks!

Bug still exists with 98 nightly!

https://ibb.co/hcpw3XH

My issue on Reddit is also not fixed. And Reddit uses HTTP2.

I have filed bug 1752270 as a followup to diagnose and fix the remaining issues.
If this bug still happens for you, please report your findings in bug 1752270.

(In reply to Ryan VanderMeulen [:RyanVM] from comment #120)

Comment on attachment 9259342 [details]
Bug 1735595 - Do not cache 408 responses r=#necko

Pretty annoying issue on a major site. Approved for 97.0b6. Also, I assume we'll want this on ESR also? And is this something we can/should have tests for?

Given it doesn't completely fix the issue, I think we don't need an uplift to ESR just yet.
I'll look into writing some tests for it.

Flags: needinfo?(valentin.gosu)

As noted in comment 128, follow-up work is happening in bug 1752270. Right now, HTTP logs are needed more than "me too" comments. Thanks!

I couldn't reproduce the issue in order to confirm it, I tried on Windows 10 x64 and on Ubuntu 20.04 x64 on all fx versions mentioned in the bug and on the recent versions.

The heading says the issue is resolved. Well it isn't. I have been having this issue for quite a few months now and I am on 104.0.2. As with other comments no issue on Edge or Chrome and I have tried all the cache and cookie cleaning and even removed my ad blocker (in case this had something to do with it).

What is most embarrassing about this is I have just persuaded two people to move from Chrome to Firefox and they are having the same issue :-(

(In reply to Morgan from comment #136)

The heading says the issue is resolved. Well it isn't. I have been having this issue for quite a few months now and I am on 104.0.2. As with other comments no issue on Edge or Chrome and I have tried all the cache and cookie cleaning and even removed my ad blocker (in case this had something to do with it).

What is most embarrassing about this is I have just persuaded two people to move from Chrome to Firefox and they are having the same issue :-(

Thanks for the feedback.
I'd suggest to file a new bug. Also, could you try to record a http log and attach to the new bug? Thanks.

Flags: needinfo?(morgan.bryan)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: