Moodle
  1. Moodle
  2. MDL-18696

Global search runs out of memory way below the PHP memory limit

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.9.4
    • Fix Version/s: None
    • Component/s: Global search
    • Labels:
      None
    • Affected Branches:
      MOODLE_19_STABLE
    • Rank:
      2356

      Description

      Global search cron job stops with this error:

      <b>Fatal error</b>: Allowed memory size of 50331648 bytes exhausted (tried to allocate 2564047 bytes) in <b>E:\Website Files\moodle\search\documents\physical_ppt.php</b> on line <b>50</b><br />

      This is odd because I have set php's memory limit to 128MB. Upping that value has no effect whatsoever.

        Activity

        Hide
        Valery Fremaux added a comment -

        Hi Matt,

        historically was the cron hard bumped to 48Mo.

        You can get rid of this limit in cron_php5.php in the search engine.

        I'll change the code for testing if the actual memory limit is over the hard bound limit so letting the system override this.

        cheers.

        Show
        Valery Fremaux added a comment - Hi Matt, historically was the cron hard bumped to 48Mo. You can get rid of this limit in cron_php5.php in the search engine. I'll change the code for testing if the actual memory limit is over the hard bound limit so letting the system override this. cheers.
        Hide
        Michael de Raadt added a comment -

        Thanks for reporting this issue.

        We have detected that this issue has been inactive for over a year has been recorded as affecting versions that are no longer supported.

        If you believe that this issue is still relevant to current versions (2.1 and beyond), please comment on the issue. Issues left inactive for a further month will be closed.

        Michael d;

        lqjjLKA0p6

        Show
        Michael de Raadt added a comment - Thanks for reporting this issue. We have detected that this issue has been inactive for over a year has been recorded as affecting versions that are no longer supported. If you believe that this issue is still relevant to current versions (2.1 and beyond), please comment on the issue. Issues left inactive for a further month will be closed. Michael d; lqjjLKA0p6
        Hide
        Michael de Raadt added a comment -

        I'm closing this issue as it appears to have become inactive and is probably not relevant to a current supported version. If you are encountering this problem or one similar, please launch a new issue.

        Show
        Michael de Raadt added a comment - I'm closing this issue as it appears to have become inactive and is probably not relevant to a current supported version. If you are encountering this problem or one similar, please launch a new issue.

          People

          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: