Last modified: 2013-06-24 19:47:18 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 T52015, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 50015 - Parsoid 500 error on some articles.
Parsoid 500 error on some articles.
Status: RESOLVED FIXED
Product: Parsoid
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: High major
: ---
Assigned To: Gabriel Wicke
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-22 10:32 UTC by Oliver Keyes
Modified: 2013-06-24 19:47 UTC (History)
3 users (show)

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


Attachments

Description Oliver Keyes 2013-06-22 10:32:02 UTC
Attempts to edit (for example) https://en.wikipedia.org/wiki/Yellow_Submarine_%28song%29 leads to parsoid loading for 25 seconds and then choking and dying with a non-user-friendly error. It's the choking and dying I'm most worried about, however, because I don't know how many articles this covers - it appears to have started last night (something in the new deployment?)
Comment 1 Erik Moeller 2013-06-23 03:22:29 UTC
Confirmed in Chrome/Ubuntu.
Comment 2 James Forrester 2013-06-23 19:03:32 UTC
Issue appears to be in "cleanUpLIHack":

http://parsoid.wmflabs.org/en/Yellow_Submarine_%28song%29
Comment 3 ssastry 2013-06-23 19:47:12 UTC
This bug affects about 0.01% of the pages (http://parsoid.wmflabs.org/stats).  The fix for this has been merged (https://gerrit.wikimedia.org/r/#/c/69956/).  Deploying a newer version of Parsoid code will fix this.
Comment 4 ssastry 2013-06-23 19:48:30 UTC
I meant to paste http://parsoid.wmflabs.org:8001/topfails which shows about 16 crashers in 160K pages.
Comment 5 Gabriel Wicke 2013-06-24 16:01:07 UTC
This will be deployed this morning PDT.

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


Navigation
Links