Last modified: 2013-04-30 08:56:52 UTC
Created attachment 8733 [details] Wikitext that produces the server error The page [[:de:Benutzer_Diskussion:Karl_Bednarik]] can't be shown, neither does it parse via API. I hunted it down to the attached input, which gives this server error when previewing: Request: POST http://de.wikipedia.org/w/index.php?title=Wikipedia:Spielwiese&action=submit, from xxx.xxx.xxx.xxx via sq40.wikimedia.org (squid/2.7.STABLE7) to 10.2.1.1 (10.2.1.1) Error: ERR_ZERO_SIZE_OBJECT, errno [No Error] at Sat, 02 Jul 2011 08:54:55 GMT Since once it must have been working in November 2010 this seems to be a regression in MediaWiki 1.17
I put comments around the code that produces the errors, so [[:de:Benutzer_Diskussion:Karl_Bednarik]] now shows the page without error. Use http://de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Karl_Bednarik&oldid=86416230 instead.
Best I can tell, this seems to be a segfault in PHP.
I definitely see a segfault on my system (Ubuntu 11.04 stock PHP packages); if I trim the giant array down to less than about 24 lines, it doesn't trigger. Usual suspects here are 'PCRE regex exploded when given too much data'... there've sometimes been bugs with long floating-point literals being interpreted in a bad way but usually that's infinite-loop rather than segfault. Doesn't _seem_ to matter which lines I delete, as long as I delete enough. Recommend checking if updating GeSHi from upstream helps; if not its regexes may need further fixing.
1.0.8.10 is the the newest version of GeSHi. Not sure if 1.17 is using that, or a slightly older version Not much work is actively done in this branch, and the newer version isn't stable for release Might be worth logging this upstream also
Could we get a repro with the latest version? And an upstream bug report?
This no longer throws a PHP error, but simply doesn't ouptput anything. As there are *many* numbers, this probably is the bug described in bug 45669. So I'm going to close this as a duplicate. *** This bug has been marked as a duplicate of bug 45669 ***
This works now on mw.org, so my guess was correct, and this bug was a duplicate of bug 45669.
