Last modified: 2010-04-10 15:40:48 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 T25131, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 23131 - Blanking large page results in white screen (possibly HTTP error 500)
Blanking large page results in white screen (possibly HTTP error 500)
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2010-04-10 02:57 UTC by MZMcBride
Modified: 2010-04-10 15:40 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description MZMcBride 2010-04-10 02:57:18 UTC 
When I try to blank (remove all page content) from this page, http://en.wikipedia.org/wiki/Wikipedia:WikiProject%20Stub%20sorting/Stub%20type%20sizes/data?action=edit , it consistently returns a white screen (page with no content at all) upon submit and does not save the edit. Could probably go under the "MediaWiki" or "Wikimedia" product, not really bothered by which.
Comment 1 Roan Kattouw 2010-04-10 10:03:08 UTC 
Someone else was able to blank the page since your report, see http://en.wikipedia.org/wiki/Wikipedia:WikiProject%20Stub%20sorting/Stub%20type%20sizes/data?action=history , therefore closing as WORKSFORME. Could be a server-specific bug though, I'll look through any error messages around the time of your report.
Comment 2 Roan Kattouw 2010-04-10 10:13:14 UTC 
AFAICT they were out-of-memory errors in the AbuseFilter parser, which makes sense given that it needs to apply filters to a huge diff. The 80M memory limit seems a bit low, though.
Comment 3 MZMcBride 2010-04-10 15:40:48 UTC 
Yeah, I've had this issue previously. Admins are generally capable of getting around the AbuseFilter, while it screws up editing for everyone else. Is there a bug related to this? I'm not seeing one off-hand.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links