Closed Bug 1402940 Opened 4 years ago Closed 4 years ago

blob-images: whatsapp is unusable slow (e10s loading circle, content process crashes)

Categories

(Core :: Graphics: WebRender, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jan, Unassigned)

References

()

Details

(Keywords: nightly-community)

Nightly 58 x64 20170925100307 de_DE @ Debian Testing (KDE / Radeon RX480)
gpu-process + layers hw accel + webrender + webrendest + layersfree = fine,
but with blob-images it's very slow.

Two weeks ago it crashed Nightly (content process crash). I see the e10s loading circle very often when opening Whatsapp. It's unusable slow, but only with blob-images, so I disabled blob-images.
Priority: -- → P2
Whiteboard: [wr-mvp]
Nightly 58 x64 20170928220658 de_DE @ Debian Testing (KDE / Radeon RX480).
gpu process + layers force accel + webrender (layersfree) + webrendest + blob-images

Just re-enabled blob-images: initial loading animations (incl. fade in) of https://web.whatsapp.com are now fast and smooth.
Whatsapp got an additional loading bar at the beginning.
Maybe
* whatsapp optimized something,
* I got a driver update,
* ublock origin or umatrix got an update,
* you changed something (looked over the changelog, have no idea),
* something else had a problem and got fixed (ublock origin causes javascript crashes in bug 1347984 for example, maybe there is more going on).

In the past I tested blob-images very often and whatsapp's animations (loading, open a chat, enlarge an image) were in slow motion with tendency to a hang, if there hadn't been already an e10s loading circle followed by a crash before.
Closing as WFM for now. Will leave blob-images activated. Someone who (still) sees this problem should reopen this bug.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
whatsapp changed how they do spriting of icons so it's likely that change that made things better
Priority: P2 → --
Whiteboard: [wr-mvp]
You need to log in before you can comment on or make changes to this bug.