Closed (outdated)
Project:
Flexifilter
Version:
6.x-1.x-dev
Component:
Code - Misc
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Jul 2009 at 12:34 UTC
Updated:
25 Sep 2020 at 09:01 UTC
Jump to comment: Most recent
Comments
Comment #1
avpadernoThat means 156 MB required; it is more than what Views requires, and it is a little too much for a filter.
Comment #2
alexh commentedI experienced the same issue.
If somebody is going to look into this, I can provide more details...
Comment #3
ptaff commentedSame. On my install, even a gigabyte of memory is not enough for a 5k document with 6 mediawiki-style links.
Comment #4
Joi commentedIm having the same problem. Anybody know a good lightweight wikifilter? I didnt like Pearwiki
Comment #5
Joi commentedFunnily enough after disabling flexifilter and re-enabling the module, the cronjobs do not abort anymore.
Comment #6
ferfong commentedI'm experiencing the same problem. Our php memory limit is 1g; and we're STILL getting "PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 348551251 bytes) in /var/www/html/main/sites/all/modules/flexifilter/flexifilter.components.inc"
1g for a wiki page that contains maybe 30 lines of text seems ridiculous.
Does anyone know how we can try to find where a memory leak might be?? We're using the 6.x-1.2 version.
Edit: It appears this may be caused in one instance by a badly-formed wiki with a ]] where there was no matching brackets, but I don't think typos made by users should be able to cause fatal PHP errors.......
Comment #7
ptaff commentedFound that in my case, the memory usage problem came from mismatched brackets; quite possibly a runaway loop somewhere in the code causes the memory problem.
Comment #8
sausis commentedIn case you decided to catch PHP's fatal errors, see:
http://php.net/manual/en/function.set-error-handler.php#88401
Comment #9
kevinhurley8179 commentedI am running flexifilter with citations to convert text such as [textbox:345] to an inline node teaser of node 345.
I don't have any open brackets, but flexifilter seems to still be consuming a lot of memory. When trying to save a feature article node which contains one of these replacements, I'm seeing this:
Fatal error: Allowed memory size of 167772160 bytes exhausted (tried to allocate 79240412 bytes) in /home/thesolut/public_html/sites/all/modules/flexifilter/flexifilter.components.inc on line 507
The only thing that seems to make it stop is disabling flexifilter.. but - of course then i end up with "[textbox:345]" in my article.
Comment #10
joel.schopp commentedStill around in 6.x-1.2 I get:
Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 177737149 bytes) in /home/wideop5/public_html/modules/flexifilter/flexifilter.components.inc on line 494
Comment #11
fonant commentedThe default flexifilter uses regular expressions a great deal, for quite a few different pairs of "tags". I fixed the problem on my site by removing those tags that I didn't need, leaving just the "[[...]]" links rules.
Comment #12
avpadernoI am closing this issue, which is for a not supported Drupal version.