Last modified: 2014-11-11 10:55:29 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 T52922, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 50922 - Large Pages not shown: Allowed memory size exhausted (PHP 5.5)
Large Pages not shown: Allowed memory size exhausted (PHP 5.5)
Status: UNCONFIRMED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.21.x
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
http://guide.lastchaos.bplaced.net/in...
: newphp
Depends on:
Blocks: 49975
  Show dependency treegraph
 
Reported: 2013-07-08 08:08 UTC by schoni92
Modified: 2014-11-11 10:55 UTC (History)
1 user (show)

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


Attachments
HTML-Code from the errorpage (647.03 KB, text/plain)
2013-07-08 08:08 UTC, schoni92
Details
Debug information (7.47 KB, text/plain)
2013-07-08 09:04 UTC, schoni92
Details
new Droplist (379.73 KB, text/plain)
2013-07-09 09:52 UTC, schoni92
Details

Description schoni92 2013-07-08 08:08:09 UTC
Created attachment 12776 [details]
HTML-Code from the errorpage

If a Page has a lot of '<' or '>' the following error code were given

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 339607 bytes) in /users/lastchaos/www/includes/Sanitizer.php on line 554

The Usage of memory is temporary more than 256MB but the problem is allready exsisting. In the content we use a lot of HTML-code and the '<' and '>' tag is used in this article more than 70.000 . I don't know, why this error should be happened, but it isnt working since the 1.21 version. Additionally the Server working with php version 5.5.

Another page, which includes a lot of <img>-Tags are present the same error but with an plugin while i submit it:
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 264175 bytes) in /users/lastchaos/www/extensions/TinyMCE_MW/TinyMCE_MW.php on line 297
In the attachment is the HTML-Code from the first page.


Furthermore the TinyMCE don't work with the newest php version (5.5) because the headlins dont change to the <h2> or other <hx>-HTML-Tags.
Comment 1 schoni92 2013-07-08 08:20:02 UTC
In my opinion the TinyMCE Extension is the cause for the Bugs. If i disable this extension all pages can be submitted and shown. Maybe the TinyMCE Extension should be updated for the newest WediaWiki version.
Comment 2 Andre Klapper 2013-07-08 08:40:44 UTC
Could you enable $wgShowExceptionDetails ? 
See http://www.mediawiki.org/wiki/Manual:How_to_debug


(In reply to comment #0)
> Furthermore the TinyMCE don't work with the newest php version (5.5) because
> the headlins dont change to the <h2> or other <hx>-HTML-Tags.

Is that a different problem? If yes, could you please file a separate bug report (again, a minimal testcase or good steps to reproduce are welcome)? Thanks.
Comment 3 schoni92 2013-07-08 08:44:36 UTC
(In reply to comment #1)
> In my opinion the TinyMCE Extension is the cause for the Bugs. If i disable
> this extension all pages can be submitted and shown. Maybe the TinyMCE
> Extension should be updated for the newest WediaWiki version.

Sorry my fault. the Problem with the large pages allready exist after disable TinyMCE Extension. I would open another bug report for the second bug. Ignore the coment.
Comment 4 schoni92 2013-07-08 09:03:34 UTC
(In reply to comment #2)
> Could you enable $wgShowExceptionDetails ? 
> See http://www.mediawiki.org/wiki/Manual:How_to_debug
> 
> 
> (In reply to comment #0)
> > Furthermore the TinyMCE don't work with the newest php version (5.5) because
> > the headlins dont change to the <h2> or other <hx>-HTML-Tags.


Hello,

sry for the bad Bugreport bud it is my first bugreport :)

I enable $wgShowExceptionDetails for the error already. If the page is called nothing more were shown. i safed the debuglog in seperate data, which is in the attachment.

(In reply to comment #2)
> Is that a different problem? If yes, could you please file a separate bug
> report (again, a minimal testcase or good steps to reproduce are welcome)?
> Thanks.

I want to do this in the afternoon.
Comment 5 schoni92 2013-07-08 09:04:59 UTC
Created attachment 12777 [details]
Debug information

The Debuginformation with the following typs of debug:
error_reporting( -1 );
ini_set( 'display_errors', 1 );
ini_set( 'display_startup_errors', 1);
$wgShowExceptionDetails = true;
$wgDebugToolbar = true;
$wgShowDebug = true;
$wgDebugComments = true;
$wgShowSQLErrors = true;
$wgDebugDumpSql  = true;
$wgShowDBErrorBacktrace = true;
Comment 6 schoni92 2013-07-08 09:32:38 UTC
For the TinyMCE_MW heading problem is another bug report:
https://bugzilla.wikimedia.org/show_bug.cgi?id=50928
I hope this bug report is better :)
Comment 7 schoni92 2013-07-09 09:49:45 UTC
Another important information:

I debuged the submit action like the Debug information.txt in the attachment. The function Parser::replaceVariables is called very often. If I comment the function between wfProfileIn( __METHOD__ ); and 	wfProfileOut( __METHOD__ ); the large site would be saved. If the function is non-comment the large site didn't saved and I get the error. Maybe this could be the problem.

Furthermore I rework the HTML code of the page and now i dont get any problem, only a blank page, if i submit the page. The HTML code is a little bit smaller as the first (~80kB). But the submit problem still appear.
Comment 8 schoni92 2013-07-09 09:52:47 UTC
Created attachment 12801 [details]
new Droplist

Here is the new HTML-Code from the large page. If it is submit with the TinyMCE_MW editor, there appear a balnk page.
Comment 9 Andre Klapper 2014-04-29 15:49:09 UTC
Aaron: Could you take a look at this (comment 5 and comment 7), in case you have an idea what's going wrong here?

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


Navigation
Links