= Description = ## Please read this page. Lines prefixed with ## such as this one are comments, ## you can remove them (except for those after the "Plan" section.) ## Please follow the instructions given in those comments and the text. ## After creating the bug page, please subscribe to it! We may have questions ## that only you can answer, and if you get email when your bug changes it'll ## be much faster to get it fixed since you can answer the questions! If an user do a single stupid fulltext search, the memory consumption goes too high. Depend on the environment of the moinmoin this can lead to several unwanted problems. == Steps to reproduce == ## Describe the steps needed to reproduce the bug. If we can't reproduce it, we probably can't fix it. I told ThomasWaldmann what the problem is<>, in general: 1. Do a search 2. Memory goes up and up (a single process, from ~60MB to 700MB) 3. After a few seconds or minutes you either got your search back or process get killed (to much memory usage) and error message is shown == Example == ##Add URL that show the bug, screenshot or test wiki markup that fail... ##URL: After a few seconds the memory goes form ~ 60MB up to 800MB, with a single search query! {{attachment:screenshot.png}} == Component selection == * action/fullseach.py * maybe xapian == Details == ## If a traceback is not available, please fill in the details here: || '''!MoinMoin Version''' || 1.9.3 || || '''OS and Version''' || Ubuntu || || '''Python Version''' || 2.5 || || '''Server Setup''' || Apache / mod_wsgi (5 processes, 15 threads)|| || '''Server Details''' || 4 GB Memory / P4 2.6GHZ || || '''Language you are using the wiki in''' (set in the browser/UserPreferences) || de || I could also reproduce the same problems under an different server (16GB Memory, Xeon 8x2.33GHz): * latest moin from hg 1.9.x * python 2.7 * xapian 1.2.7 * uwsgi 0.9.9.1 * nginx 1.0.6 == Workaround == ## How to deal with the bug until it is fixed * disable fulltext search * or filter out some searches = Discussion = A workaround like [[http://moinmo.in/MarcelH%C3%A4fner/Bleeding%20Edge#Limit_Search|this]] is not enough, we need a better filter or generaly a better result list management (less memory usage in generaly). = Plan = ## This part is for Moin``Moin developers: * Priority: * Assigned to: * Status: ---- ## If you are a moin core developer, replace the category to Category* in these cases: ## Category MoinMoinNoBug - if this is not a bug. ## Category MoinMoinBugConfirmed - if you can confirm the bug on current code. ## Category MoinMoinBugFixed - after the bug is fixed in current code. CategoryMoinMoinBug