Bug 198857
| Summary: | [GTK] Some site is unbearably slow to load | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Andrea Giammarchi <andrea.giammarchi> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | Normal | CC: | bugs-noreply, kdwkleung, mcatanzaro, nekohayo, pnormand |
| Priority: | P3 | Keywords: | Gtk |
| Version: | WebKit Local Build | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Bug Depends on: | |||
| Bug Blocks: | 245783 | ||
Andrea Giammarchi
If I try to load https://twitter.com/WebKitGTK as example, it takes forever, and sometimes it finishes only after reloading it.
I am on latest ArchLinux and GNOME 3.32.2, on Intel® Core™ i7-8565U CPU @ 1.80GHz × 8, and Intel® HD Graphics (Whiskey Lake 3x8 GT2), and 16GB of RAM.
On Safari, everything is just fine, so I wonder if this issue is specific to the GTK port.
Thanks.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Michael Catanzaro
Probably bug #197558.
*** This bug has been marked as a duplicate of bug 197558 ***
Philippe Normand
That Twitter page doesn't have videos, so unrelated to bug #197558
Andrea Giammarchi
Not only that, but I have no freezing issues, rather white page and no site whatsoever, it hangs for too long.
True that it's hard to find other site with a similar issue, and the issue itself is quite intermittent.
Andrea Giammarchi
actually, opening https://extensions.gnome.org/ is super slow/problematic too
Kdwk
This issue can no longer be observed in the latest WebKitGTK.
Michael Catanzaro
In my unscientific testing, it takes 4 seconds to load the tweet feed in Firefox but 12 seconds to do so in Epiphany Tech Preview, so that's really not looking very great to me. Andrea, are you still having trouble with https://twitter.com/WebKitGTK?
Andrea Giammarchi
GNOME Web works fine ... twitter itself had an issue with its Service Worker recently, so I wouldn't out the delay you are observing into WebKitGTK
Michael Catanzaro
OK, let's close this then. Probably fixed sometime between when you reported it and now.