Last modified: 2014-11-20 03:31:19 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 T75639, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 73639 - "Maximum function nesting level" fatal when visiting an imported page with nested conversations
"Maximum function nesting level" fatal when visiting an imported page with ne...
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-20 03:15 UTC by Matthew Flaschen
Modified: 2014-11-20 03:31 UTC (History)
5 users (show)

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


Attachments

Description Matthew Flaschen 2014-11-20 03:15:45 UTC
I imported https://www.mediawiki.org/wiki/VisualEditor/Feedback into Flow with the LQT importer (plus some small changes for https://gerrit.wikimedia.org/r/#/c/172925/ that are probably not relevant to this bug).

The import crashed (bug 73638), but a lot of stuff was already imported by then.  However, when I visit it, I get:

"Fatal error: Maximum function nesting level of '200' reached, aborting"

The stack is https://phabricator.wikimedia.org/P98 .

It seems that the nesting level of a topic may influence the nesting level of the function stack, and cause it to go over the limit.
Comment 1 Matthew Flaschen 2014-11-20 03:31:19 UTC
This error comes from xdebug.max_nesting_level.

XDebug is not enabled in production, so we shouldn't have to worry about this.

I confirmed it can be worked around locally by raising the limit or switching to HHVM.

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


Navigation
Links