Last modified: 2014-01-02 21:37:27 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 T61164, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 59164 - CirrusSearch: forceSearchIndex.php leaks memory
CirrusSearch: forceSearchIndex.php leaks memory
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
CirrusSearch (Other open bugs)
unspecified
All All
: High normal (vote)
: ---
Assigned To: Nik Everett
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-31 14:44 UTC by Nik Everett
Modified: 2014-01-02 21:37 UTC (History)
3 users (show)

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


Attachments

Description Nik Everett 2013-12-31 14:44:00 UTC
forceSearchIndex.php leaks memory.  After queueing three million titles the process takes up ~2GB of memory.
Comment 1 Gerrit Notification Bot 2013-12-31 16:19:42 UTC
Change 104745 had a related patch set uploaded by Manybubbles:
Leak less memory in forceSearchIndex.php

https://gerrit.wikimedia.org/r/104745
Comment 2 Gerrit Notification Bot 2013-12-31 17:32:47 UTC
Change 104745 merged by jenkins-bot:
Leak less memory in forceSearchIndex.php

https://gerrit.wikimedia.org/r/104745
Comment 3 Gerrit Notification Bot 2014-01-02 21:18:37 UTC
Change 105091 had a related patch set uploaded by Manybubbles:
Build fixed size chunks when indexing

https://gerrit.wikimedia.org/r/105091
Comment 4 Gerrit Notification Bot 2014-01-02 21:27:20 UTC
Change 105091 merged by Chad:
Build fixed size chunks when indexing

https://gerrit.wikimedia.org/r/105091
Comment 5 Nik Everett 2014-01-02 21:37:27 UTC
We've worked around this in two ways:
1.  Leaking less memory.
2.  Letting you spit out fixed sized chunks and telling you to do so in the README.

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


Navigation
Links