Changing network.preload to false breaks webpages
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(firefox98 affected, firefox99 affected, firefox101 affected, firefox102 affected, firefox103 affected, firefox111 affected)
People
(Reporter: hjstephens09, Assigned: skyschub)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
|
1.76 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:98.0) Gecko/20100101 Firefox/98.0
Steps to reproduce:
I've had two instances where pref("network.preload", false); causes the webpage to not load or crash.
https://graad.eu/(see https://github.com/yokoffing/Better-Fox/issues/44)https://www.mg.superesportes.com.br(see https://github.com/yokoffing/Better-Fox/issues/53)
Actual results:
Site either does not load properly or crashes altogether.
Expected results:
Site should still load properly.
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•4 years ago
|
||
Greg, can you find someone to take a look?
Comment 3•4 years ago
•
|
||
I've tried to reproduce this locally. The first site https://graad.eu/ was loaded completely with network.preload disabled, so there might be something changed at the server side.
When I tried to load the second site https://www.mg.superesportes.com.br with network.preload disabled, I've seen that the tab hung and my CPU usage was 100%. After disabling javascript, the site can be loaded partially, so I think this is a site issue and I'd like to change the component to Web Compatibility.
Updated•4 years ago
|
Comment 4•4 years ago
|
||
We can try to diagnose. But if it creates a crash and Chrome/Safari in the same circumstances would not crash, it's definitely a Gecko Core issue.
Comment 5•4 years ago
|
||
(In reply to Karl Dubost💡 :karlcow from comment #4)
We can try to diagnose. But if it creates a crash and Chrome/Safari in the same circumstances would not crash, it's definitely a Gecko Core issue.
I don't know if there is a way to disable preload for Chrome/Safari, so it's probably not easy to test the behavior of Chrome/Safari under the same circumstances.
Comment 6•4 years ago
|
||
I didn't have a crash but the memory footprint keeps increasing even on an inactive window. 20 Mo by 20 Mo
This is a profile for graad.eu
https://share.firefox.dev/3sVqgiI
Another one with the project already loaded
https://share.firefox.dev/3h4m3U2
Comment 7•4 years ago
|
||
Once I'm closing the tab for graad.eu, I'm getting back the memory, but not everything.
Comment 8•4 years ago
•
|
||
Comment 9•4 years ago
|
||
I would recommend the reporter to contact the websites for having better fallbacks.
| Reporter | ||
Comment 10•4 years ago
|
||
I've tried to reproduce this locally. The first site
https://graad.eu/was loaded completely withnetwork.preloaddisabled, so there might be something changed at the server side.
The first site, https://graad.eu/, will load but the CSS is broken on the page with network.preload set to false.
Comment 11•4 years ago
|
||
The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.
Comment 12•3 years ago
|
||
Following the steps to reproduce, I was able to reproduce the issue on the second page https://www.mg.superesportes.com.b, where the page does not load and Nightly prompts an error message:
For the first page: https://graad.eu/, the CSS is indeed broken:
This was observed with the pref network.preload set to FALSE
Tested with:
Browser / Version: Firefox Release 101.0.1 (64-bit)/ Firefox Nightly 103.0a1 (2022-06-22) (64-bit) /Microsoft Edge Version 102.0.1245.44 (Official build) (64-bit)
Operating System: Windows 10 PRO x64
Notes:
- Reproducible regardless of the status of ETP.
- Reproducible on the latest build of Firefox Nightly and Release.
- Works as expected using Edge.
Updated•3 years ago
|
Comment 13•3 years ago
|
||
Since nightly and release are affected, beta will likely be affected too.
$For more information, please visit auto_nag documentation.
Updated•3 years ago
|
| Assignee | ||
Comment 15•1 year ago
|
||
If you disable a feature of the Web Platform, and then use a site that depends on said feature, then yes, it breaks. This isn't really anything we can work on.
Description
•