webkit.org is slow to load or displays a "403 Forbidden" error
Categories
(Core :: XPCOM, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox-esr115 | --- | unaffected |
| firefox117 | --- | unaffected |
| firefox118 | --- | ? |
| firefox119 | --- | affected |
People
(Reporter: cpeterson, Unassigned)
References
(Regression, )
Details
(Keywords: regression)
Justin, I believe this bug is a regression from your timer fix for bug 1831014. I used mozregression to bisect this problem to this pushlog:
Bug 1831014 landed in Nightly 118, but I'm not able to reproduce this bug in Beta 118. Are those timer changes only enabled in the Nightly channel?
Steps to reproduce
- Open a Private Window in Nightly 118+. A Private Window isn't strictly necessary to reproduce this bug, but it seems to make reproducing it easier (perhaps due to some caching of content I've loaded previously?).
- Try to load https://webkit.org/blog/14445/webkit-features-in-safari-17-0/
Expected results
The page should load quickly and fully.
Actual results
The page loads very slowly, some elements (like the CSS or the word cloud image) fail to load, or Firefox displays a "403 Forbidden" error.
I'm using Windows 11 Insider Beta.
|
||
Comment 1•2 years ago
|
||
It fails to load for me on Edge on Ubuntu. I doubt this is Firefox issue.
|
||
Comment 2•2 years ago
|
||
Hmm, this is a little bit weird. While doing some testing just right now, I was able to reproduce this problem (getting a 403 when trying to load the cited page, sometimes after some time of spinning) with my installed version of Firefox, which is 117.0.1. I'm a bit confused about how to know what change is in what release, but, if I understand correctly, 117.0.1 does not contain the cited change, is that right? (I am on Windows as well.)
Then, after consistently failing to load quite a number of times in 117.0.1 it has now started loading consistently. (And I just tried in my own locally-built 119.something Nightly and it consistently loaded as well.)
I'm wondering if there might be something else in play here.
|
Reporter | |
Comment 3•2 years ago
|
||
The page is loading consistently and quickly for me now. And since Edge on Ubuntu was also affected, I guess this problem was an intermittent server issue. Resolving as WFM.
https://webkit.org/blog/14445/webkit-features-in-safari-17-0
Description
•