Last modified: 2012-12-17 14:51:58 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 T44266, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 42266 - Browser unresponsive for some seconds on pages with high number of audio files
Browser unresponsive for some seconds on pages with high number of audio files
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
TimedMediaHandler (Other open bugs)
master
All All
: Unprioritized normal (vote)
: ---
Assigned To: Michael Dale
https://commons.wikimedia.org/wiki/Ca...
: performance
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-19 16:26 UTC by Andre Klapper
Modified: 2012-12-17 14:51 UTC (History)
3 users (show)

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


Attachments

Description Andre Klapper 2012-11-19 16:26:33 UTC
Forwarding from https://commons.wikimedia.org/wiki/Commons:Village_pump#New_html5_player_issues .
I can confirm this with the example URL in Firefox 16.0.2.

I'm having an issue opening pages with high numbers of audio files (which is often the case with categories like https://commons.wikimedia.org/wiki/Category:Ogg_files_of_music_by_Frederic_Chopin ): 

Browser window (Firefox) or tab (Chromium) becomes unresponsive for about 20—30 seconds until that page can be successfully viewed/scrolled. It seems that the loading of the player is the bottleneck. A possible solution would be to load and render the player conditionally, only when the user decides to play a media file.
Comment 1 db [inactive,noenotif] 2012-11-19 19:52:03 UTC
related: bug 42071
Comment 2 Jan Gerber 2012-12-17 14:51:58 UTC
looks like the changes in bug 42071 fix this, please reopen with additional information if the problem still exists.

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


Navigation
Links