Re: [Semediawiki-user] Debugging PHP Fatal error: Allowed memory size exhausted

[Christoph B. <cbu...@ir...>]

Thanks so far, Samuel, John, David

I forgot that I had tested it earlier on my home installation which works 
well. Copy&Pasting the result from DT into the hosted setup by manually 
editing the target page funnily yields the same error, thus it must be 
somewhere inside MediaWiki that memory is consumed.
Shortening the input finally yields an error msg actually displayed in the 
browser, and interestingly the first bigger chunk of allocated memory that 
turns up:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to 
allocate 267219 bytes) in /XXX/w/includes/parser/Parser.php on line 420

Replacing the single Chinese characters that I am trying to write with simple 
'a's works. I thus assume it's a hidden issue with encoding of non-ASCII 
characters. I can save the pure content, but once I put that into the template 
call: bang.

I should probably ask on the MediaWiki list. Digging through parser/Parser.php 
now.

-Christoph

Am Freitag, 6. August 2010 schrieben Sie:
> If you are uploading a 54kb file, you are most certainly not running out of
> memory because of the file size.
> 
> What this sounds like to me is something that is trying to process the file
> that you uploaded is getting caught in an endless loop.  Each time through
> the loop it allocates a little more memory.  Before long, memory is
> exhausted.
> 
> I would suggest breaking down your input file into its most elementary
> example.  Make the smallest file that can illustrate the problem.  Then not
> only will you know what it is about that file that is causing you the
> headache, but you will have an example that you can offer so the developer
> can do something about it.
> 
> On Thu, Aug 5, 2010 at 4:52 PM, Christoph Burgmer 
<cbu...@ir...>wrote:
> > Am Donnerstag, 5. August 2010 schrieb Samuel Lampa:
> > > On 08/05/2010 09:14 PM, Christoph Burgmer wrote:
> > > > I'm not too experienced with PHP let alone SMW internals. What
> > > > possibilities do I have to find the issue at hand here? Increasing
> > > > memory is not an option.
> > > 
> > > Just to make sure, why is it not an option? In case it is because you
> > > don't have access to the ini file, you typically can still increase it
> > > by addning a line like this in LocalSettings.php:
> > > 
> > > ini_set('memory_limit', '64M');
> > > 
> > > The only other option I can see (though others might have more
> > > suggestions) would be to temporarily disable some extensions.
> > 
> > I just tried to add the above line to the top of LocalSettings.php but
> > would
> > still get the same error. Same with the equivalent put into .htaccess.
> > So the limit is not even increased it seems.
> > 
> > The only thing that changes, is the place where the error is raised. But
> > this
> > seems unconnected to the memory limit setting.
> > 
> > I don't consider the file to be very big, so I wonder where all the
> > memory goes
> > to. Maybe I should take a look at how exactly DT parses the document.
> > 
> > -Christoph
> > 
> > 
> > -------------------------------------------------------------------------
> > ----- This SF.net email is sponsored by
> > 
> > Make an app they can't live without
> > Enter the BlackBerry Developer Challenge
> > http://p.sf.net/sfu/RIM-dev2dev
> > _______________________________________________
> > Semediawiki-user mailing list
> > Sem...@li...
> > https://lists.sourceforge.net/lists/listinfo/semediawiki-user