Last modified: 2009-12-29 14:29:47 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 T23965, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 21965 - Special:MostLinked page crash
Special:MostLinked page crash
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-12-29 13:55 UTC by Janne Pulkkinen
Modified: 2009-12-29 14:29 UTC (History)
1 user (show)

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


Attachments

Description Janne Pulkkinen 2009-12-29 13:55:03 UTC
It seems that opening multiple tabs of Special:MostLinked pages and repeatedly refreshing them causes the site to crash.

I heard about this from some person in an IRC channel and after trying it myself it made the site unaccessible for few minutes. This applies to all users of the site.

My guess is that the software somehow hangs while trying to compose a list of most linked pages.

Wikipedia, homever, has blocked this special page from being accessed.
Comment 1 Roan Kattouw 2009-12-29 14:29:47 UTC
Special:Mostlinked is an expensive special page, and generating it is stressful for the database. If your wiki is large or if there are many generation attempts going on at the same time, the slowness you described can happen.

You can set $wgMiserMode = true; to disable such expensive features; you can then use the updateSpecialPages.php maintenance script to periodically update these pages rather than having them regenerated every time someone views them.

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


Navigation
Links