1289866 - Very slow, choppy performance of SVG compared to Chrome on same device (example included)

Status: RESOLVED DUPLICATE of bug 1686590

(Firefox for Android Graveyard :: Toolbar, defect, P5)

Description

[donrhummy]

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

Steps to reproduce:

Visited this page on both Firefox Beta and Chrome on Android: http://vallandingham.me/gates_bubbles/


Actual results:

It was very, very slow and choppy. And clicking on a circle resulted in text-selection.


Expected results:

It should have been as fast as Chrome was. Chrome ran well without any choppiness. it was slower than a desktop but not by a lot.

Using Nexus 5X.

Comment 1

[Simon Basca [:SimonB]]

Thank you for reporting this issue. I was able to reproduce the issue using the STR from the description.

Comment 2

[Kartikaya Gupta (email:[e-mail])]

(In reply to donrhummy from comment #0)
> And clicking on a circle resulted in
> text-selection.

That part is bug 1286882. We can use this bug to track the slow/choppiness. It's pretty slow on 47 as well.

Comment 3

[Kartikaya Gupta (email:[e-mail])]

Here's a profile of some of the page load, while the SVG thing is animating: https://cleopatra.io/#report=31325079bdae96c68eee959838c1e0de2388a14b

Unfortunately it doesn't look like it has full symbol information, but even so a lot of the time is spent in painting and script.

Comment 4

[Kartikaya Gupta (email:[e-mail])]

Although Firefox nightly is still choppier than Chrome, it's a lot faster than I remember it being. So there has been improvement here, but maybe there is still room for more.

Comment 5

[mockingbird]

Kartikaya - 

SVG Rendering is still very much broken on Firefox.

Please see this benchmark:

https://testdrive-archive.azurewebsites.net/performance/chalkboard/

The benchmark crashes.  about:support reports this failure:

CP+[GFX1-]: Failed to allocate a surface due to invalid size (CDT) Size(14321,9828)

On Chromium 59, the score is 8 seconds.

Thanks

Comment 6

[Kartikaya Gupta (email:[e-mail])]

Thanks for the report - however it would be best to file a new bug for this issue as it will likely need some detailed investigation and might have different root causes/fixes than the gates_bubble example previously given. Specially if it is crashing for you. Thanks!

Comment 7

[Jan Bösenberg]

The test case at http://vallandingham.me/gates_bubbles/ runs smoothly on Firefox 60, so this issue can probably be closed.

The chalkboard test case mentioned in comment 6 has been reported at least in four other issues (the main one is probably 1387841 ), so this is not needed here anymore.

Comment 8

[Firefox Bug Husbandry Bot]

Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195

Needinfo :susheel if you think this bug should be re-triaged.

Comment 9

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.

Comment 10

[Daniel Holbert [:dholbert] (PTO until 2/24)]

It seems this was a core Gecko performance bug, not a Firefox-for-Android bug. It looks like someone filed a github issue about it (following the bot's instructions in comment 9), https://github.com/mozilla-mobile/fenix/issues/17216 , which then resulted in a new Gecko bug being filed after it was determined that this was in fact not a browser-frontend-bug. That eventual bug is bug 1686590.

I'm duping this forward to bug 1686590 to link them up. (There's more recent info on the new bug so it's probably a better place for someone to start, when someone can take a look at fixing this.)