Using 131.03 here and there are no issues whatsoever. Actually there hasnt been any issues or slow yande.re for me since i recently formatted Windows 11 due to other issues. Could be a Windows 11 component that has changed/updated and broken firefox as well.
Sorry if it sounded like I'm expecting a fix from the devs. This is absolutely a regression on the FF side, since it's not reproducing in the older releases. Just wanted to share my findings, since here seems to be the place where most affected users would reach first. Maybe someone will have an idea what exactly is causing this, so that we can file a report to Mozilla.
Just checked 131.03 and it's still reproducing for me. The thing is, you have to browse for some time (about 10-20 pages) before it starts happening. First it'll occasionally fail to load thumbnails and eventually stops loading pages at all. After a FF re-install or upgrade it resolves initially but starts happening again eventually.
I've also checked in a clean Ubuntu VM to make sure it's not something OS-related (initially I've tested in Windows) and it's reproducing there as well.
Just checked 131.03 and it's still reproducing for me. The thing is, you have to browse for some time (about 10-20 pages) before it starts happening. First it'll occasionally fail to load thumbnails and eventually stops loading pages at all. After a FF re-install or upgrade it resolves initially but starts happening again eventually.
I've also checked in a clean Ubuntu VM to make sure it's not something OS-related (initially I've tested in Windows) and it's reproducing there as well.
Mozilla doesn't accept webcompat issues for NSFW sites, I already tried.
I'm on win10, though I'm experiencing the issue on Android as well.Ew said:
Using 131.03 here and there are no issues whatsoever. Actually there hasnt been any issues or slow yande.re for me since i recently formatted Windows 11 due to other issues. Could be a Windows 11 component that has changed/updated and broken firefox as well.
Question: do you have problems with Konachan too, since both sites use Moebooru?
I'm on Windows 10 and Xubuntu Linux and this issue occurs on both, so it's not an OS issue.Ew said:
Could be a Windows 11 component that has changed/updated and broken firefox as well.
I have no problems at all with Konachan. Yande.re is the one and only site I have seen having this problem.Trit said:
Question: do you have problems with Konachan too, since both sites use Moebooru?
For me it is immediate. As soon as I start browsing the site it has trouble loading thumbnails and images. It has moments when it loads quickly, but most of the time it is unbearably slow or just fails to load at all.Elringus said:
The thing is, you have to browse for some time (about 10-20 pages) before it starts happening.
Konachan works fine for me.Trit said:
Question: do you have problems with Konachan too, since both sites use Moebooru?
Given how much trouble it is causing lately, I promise I will look into it as soon as possible (preferably sooner than later)
I've disabled http3 for now, anyone still have problem with Firefox?
A quick poke around doesn't show anything immediately obvious. That is to say that, with http2 only, the site seems to be working fine.Checkmate said:
I've disabled http3 for now, anyone still have problem with Firefox?
Edit: files.yande.re seems to be randomly shitting the bed.
I'm not noticing any change, I'm still unable to load most images.Checkmate said:
I've disabled http3 for now, anyone still have problem with Firefox?
Images that don't load at first load for me when refreshing the page cleaning the cache (Ctrl + F5). Maybe this will come in handy for someone.
I was having to Ctrl+F5 to get images to load yesterday, but it appears to have cleared up today and is working well. Must have been a residual caching issue.
As of right now performance in Firefox is good, best it has been in a very long time in fact.
As of right now performance in Firefox is good, best it has been in a very long time in fact.
Now back to having to Ctrl+F5 every other image. Very strange.
i'm facing same problem in danbooru
Go complain there, then.Katsura_Kotonoha said:
i'm facing same problem in danbooru
Just wanted to chime in, and say that I've switched to Firefox now too, and I did the http3 disable and there aren't anymore unloaded thumbnails, or images that fail loading.
It's also like another user said.
When I am browsing on my phone, via Wifi from the router, Firefox has more often than not issues loading images, but when I go to Roaming Data from my Phone Provider, I don't have those issues, very strange.
I could maybe see some faulty Internet access point somewhere along the way, but I am not tech-savvy enough to know really what's going on.
It's also like another user said.
When I am browsing on my phone, via Wifi from the router, Firefox has more often than not issues loading images, but when I go to Roaming Data from my Phone Provider, I don't have those issues, very strange.
I could maybe see some faulty Internet access point somewhere along the way, but I am not tech-savvy enough to know really what's going on.
Quickly chiming in on this issue here: Using Firefox 133.0.3 on Manjaro Linux, and I can confirm disabling http3 fixes the issue completely.

phenius
There are many websites out there using nginx and, so far, I haven't seen a single report of this issue occurring on any other site. If multiple users are experiencing the same issue which is only occurring on a single site running on software that other, unaffected, sites are also using, then it seems clear to me that the issue lies with the site and not the browser.
In a case like this, I feel it is the responsibility of the web site developer to make sure their site is compatible and working properly with the most common web browsers. You can't expect Mozilla to care about a single website not working, nor can you expect end users to go through advanced troubleshooting/configuration changes just to make one site work. Most users will just leave if it doesn't work as expected.
With all of that said, I do understand that this site is something of a passion project and doesn't have a huge team of developers working on it. I can completely understand not being able to figure out a problem, but I don't think it's right to try and pawn the problem off on the users or Mozilla. It would be far better to simply say "I've tried to investigate this and haven't been able to find the root cause or a solution so far."
Just my two cents, for whatever it's worth.