Last modified: 2014-01-29 01:21:34 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T57766, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 55766 - Flow: VE takes significant time to manifest
Flow: VE takes significant time to manifest
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
unspecified
All All
: Lowest normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-15 22:59 UTC by Chris McMahon
Modified: 2014-01-29 01:21 UTC (History)
7 users (show)

See Also:
Web browser: Google Chrome
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Chris McMahon 2013-10-15 22:59:13 UTC
We have been encountering a number of performance issues and race conditions with VE and Chrome in recent times, this is probably one more of those. 

* In a fresh instance of Chrome 30 or Chrome 29, as a logged in user, visit https://en.wikipedia.beta.wmflabs.org/wiki/Special:Flow/Flow_QA

* Enter a Message topic

The VE controls and CE field take significant time to appear while the user sees a spinner.  For an example causing a failure in a browser test, see https://wmf.ci.cloudbees.com/job/Flow-en.wikipedia.beta.wmflabs.org-linux-chrome/12/testReport/(root)/Create%20new%20topic%20logged%20in/Add_new_Flow_topic/ .  Note the test times out with the spinner still visible after 5 seconds. 

This is not seen in Firefox
Comment 1 spage 2013-10-17 17:14:11 UTC
The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/324, but people from the community are welcome to contribute here and in Gerrit.
Comment 2 Oliver Keyes 2013-10-28 20:02:55 UTC
This is likely a problem with the Labs instance; no varnish == no caching of VE elements :/. Unfortunately that means it's something we're probably not going to be able to track or test properly until we go into deployment on production. Closing as WONTFIX since LATER is no longer available.
Comment 3 Bartosz Dziewoński 2013-10-28 20:04:44 UTC
("RESOLVED LATER" was replaced with the "lowest" priority. Might want to use that instead.)
Comment 4 Oliver Keyes 2013-10-28 20:06:55 UTC
Aha; thanks for letting me know :).
Comment 5 Andrew Garrett 2013-11-06 03:13:07 UTC
I've tested it on my own box. It's this call that takes the long time:

'http://localhost/mw-dev/load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Ccore%2Cdata%2Cicons-vector%2Cstandalone%7Cext.visualEditor.viewPageTarget.icons-vector%7Coojs%2Coojs-ui%2Crangy%7Cunicodejs.wordbreak&skin=vector&version=20131106T030133Z&*'

This typically returns in ~6 seconds. However, I've found that sometimes it works in ~200ms. When that happens, VE loads quickly on my local box.

So it does indeed seem to be caching, of a particular ResourceLoader resource.
Comment 6 Maryana Pinchuk 2014-01-29 01:21:34 UTC
We removed the VE option in Flow long, long ago :) 

People should feel free to reopen this when we actually have the VE in Flow option up and running again.

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


Navigation
Links