125M memory limit exhausted when editing nearly empty page
Closed, ResolvedPublic
Actions

Assigned To

None

Authored By

	Sj
	Mar 3 2008, 3:35 PM

Description

This simple wiki page : http://wiki.laptop.org/go/Activities/translations 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/wiki.laptop.org/includes/Parser.php 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.

Version: 1.10.x
Severity: normal
OS: Linux
URL: http://wiki.laptop.org/index.php?title=Activities/translations&action=submit

Details

Reference: bz13233

Event Timeline

• bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:06 PM

• bzimport added a project: MediaWiki-Page-editing.

• bzimport set Reference to bz13233.

• bzimport added a subscriber: Unknown Object (MLST).

Sj created this task.Mar 3 2008, 3:35 PM

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...

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.

I recommended installing the xdebug PHP extension, which will give you a backtrace so you might have some hope of debugging it.

Does this bug still occur after upgrade to 1.12?

mel wrote:

The upgrade appears to have fixed things - thanks! Closing downstream as well, http://dev.laptop.org/ticket/6421#comment:14.

125M memory limit exhausted when editing nearly empty pageClosed, ResolvedPublicActions

Description

Details

Event Timeline

125M memory limit exhausted when editing nearly empty page
Closed, ResolvedPublic
Actions