Last modified: 2010-05-15 15:51:55 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 13233 - 125M memory limit exhausted when editing nearly empty page
125M memory limit exhausted when editing nearly empty page
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
All Linux
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-03-03 15:35 UTC by SJ
Modified: 2010-05-15 15:51 UTC (History)
3 users (show)

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


Description SJ 2008-03-03 15:35:59 UTC
This simple wiki page : repeatedly triggers this error on saving (after successfully saving changes, as it turns out):

"Fatal error: Allowed memory size of 125829120 bytes exhausted (tried to allocate 229933 bytes) in /home/www/ on line 2717"

Version info:
  MediaWiki: 1.10.0
  PHP: 5.2.4-2ubuntu4 (apache2handler)
  MySQL: 5.0.45-3ubuntu1 

A few other pages on the same wiki, often related to translation such as the one above, have similarly triggered this class of error.
The PHP calls haven't yet been traced to see exactly what request is exhausting the memory.  I have heard of but haven't been able to reproduce cases where this error is thrown and changes are not saved.
Comment 1 Roan Kattouw 2008-03-03 15:40:03 UTC
Tweaking summary. The weird thing here is that the page is nearly empty (only contains comments), yet the parser seems to need lots of memory...
Comment 2 SJ 2008-03-04 20:34:57 UTC
It's happening now without edits on other pages; and with increasing frequency.  Basically, since this class of error was first reported a month ago, it has steadily increased in frequency, and is influenced by the # of people editing the site.   The box it's running on has 3+G of memory and had 10G of swap added the other night.  The box was also brought down by a whole raft of processes running out of memory and had to be rebooted.
Comment 3 Brion Vibber 2008-03-05 00:16:08 UTC
I recommended installing the xdebug PHP extension, which will give you a backtrace so you might have some hope of debugging it.
Comment 4 Max Semenik 2008-06-27 13:15:15 UTC
Does this bug still occur after upgrade to 1.12?
Comment 5 Mel Chua 2008-11-21 05:44:13 UTC
The upgrade appears to have fixed things - thanks! Closing downstream as well,

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