Bug 267774

Summary:

[GTK] Slow to load GMail's inbox (or search results)

Product:

WebKit

Reporter:

Jeff Fortin <nekohayo>

Component:

WebKitGTK

Assignee:

Nobody <webkit-unassigned>

Status:

NEW

Severity:

Normal

CC:

bugs-noreply

Priority:

Keywords:

Performance

Version:

Other

Hardware:

Unspecified

OS:

Linux

See Also:

https://bugs.webkit.org/show_bug.cgi?id=251336

Bug Depends on:

Bug Blocks:

245783

Attachments:

Description	Flags
Video demonstrating the issue	none
Web inspector timeline recording	none
Web inspector timeline recording - screenshot	none
sysprof recording	none
sysprof recording screenshot - entire flamegraph	none
sysprof recording screenshot - left portion of the flamegraph	none
sysprof recording screenshot - right portion of the flamegraph	none
sysprof recording screenshot - compositor marks	none

Jeff Fortin

Reported 2024-01-19 11:23:00 PST

Created attachment 469460 [details] Video demonstrating the issue Symptoms: see attached video. On my desktop machine, it takes roughly 10-12 seconds for an already logged in GMail inbox to fully load and render, when launching as a web app (but loading seems similarly slow on a regular Epiphany window). Testing parameters: * Epiphany 45.1 installed from the Fedora 39 repositories (not flatpaked), on a SSD. Cache directories are also on a SSD. * WebKitGTK 2.42.3, GStreamer 1.22.8 * Running in the Wayland version of GNOME Shell 45.3 on Fedora 39 (fully up to date) * CPU: Intel® Xeon® W3520 × 8 * GPU: Radeon R9 270 running on Mesa 23.3.3 * Launching it as a web app, like this: epiphany --application-mode \ --profile="/home/your_username/.local/share/org.gnome.Epiphany.WebApp_BigHashHere" \ "https://mail.google.com/mail/u/0/#search/gnome" I will attach sysprof captures (and convenience screenshots) and captures from the web inspector's timeline.

Attachments
Video demonstrating the issue (298.78 KB, video/webm) 2024-01-19 11:23 PST, Jeff Fortin	no flags	Details
Web inspector timeline recording (7.82 KB, application/x-xz) 2024-01-19 11:25 PST, Jeff Fortin	no flags	Details
Web inspector timeline recording - screenshot (159.58 KB, image/png) 2024-01-19 11:25 PST, Jeff Fortin	no flags	Details
sysprof recording (5.11 MB, application/x-xz) 2024-01-19 11:26 PST, Jeff Fortin	no flags	Details
sysprof recording screenshot - entire flamegraph (245.02 KB, image/png) 2024-01-19 11:26 PST, Jeff Fortin	no flags	Details
sysprof recording screenshot - left portion of the flamegraph (232.36 KB, image/png) 2024-01-19 11:26 PST, Jeff Fortin	no flags	Details
sysprof recording screenshot - right portion of the flamegraph (952.90 KB, image/png) 2024-01-19 11:27 PST, Jeff Fortin	no flags	Details
sysprof recording screenshot - compositor marks (209.16 KB, image/png) 2024-01-19 11:27 PST, Jeff Fortin	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Jeff Fortin

Comment 1 2024-01-19 11:25:11 PST

Created attachment 469461 [details] Web inspector timeline recording

Jeff Fortin

Comment 2 2024-01-19 11:25:30 PST

Created attachment 469462 [details] Web inspector timeline recording - screenshot

Jeff Fortin

Comment 3 2024-01-19 11:26:06 PST

Created attachment 469463 [details] sysprof recording

Jeff Fortin

Comment 4 2024-01-19 11:26:41 PST

Created attachment 469464 [details] sysprof recording screenshot - entire flamegraph

Jeff Fortin

Comment 5 2024-01-19 11:26:57 PST

Created attachment 469465 [details] sysprof recording screenshot - left portion of the flamegraph

Jeff Fortin

Comment 6 2024-01-19 11:27:13 PST

Created attachment 469466 [details] sysprof recording screenshot - right portion of the flamegraph

Jeff Fortin

Comment 7 2024-01-19 11:27:42 PST

Created attachment 469467 [details] sysprof recording screenshot - compositor marks

Jeff Fortin

Comment 8 2024-01-19 13:00:18 PST

For the record, this also happens on a laptop with an 8th-gen Intel "Kabylake" i5 8350U CPU and Intel UHD 620 graphics, so not caused by the Xeon/Radeon specifically. Neither machine are running HiDPI screens, they use normal 1080p 60 Hz displays.

Note You need to log in before you can comment on or make changes to this bug.