Hi there:

I'm receiving this error each time cron runs:
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 40 bytes) in /home/path/to/modules/geshifilter/geshi/geshi.php on line 1556

I can't seem to locate an error more specific than that, and am not sure how to troubleshoot. Ideas?

Drupal 5.5 (gettting ready to upgrade to latest security release).

Thanks!

Comments

soxofaan’s picture

soxofaan commented

That strange, GeSHi filter does not define a cron hook.
So it's probably another cron hook that invokes GeSHi filter code.
What other modules have you enabled, especially the ones that have a cron hook?
Is it feasible to disable those modules one per time to find out which one is the culprit?

Have you any idea of the total amount of source code in you content that gets GeSHi syntax highlighting?

Moreover, the file you mention is from the GeSHi library, not the GeSHi filter module directly. Which version of the library are you using?

cheathamlane’s picture

cheathamlane commented

Hi there:

Thanks for the quick response!

I'm using "Subscriptions", among other modules -- but believe this is really the only add-on which relies on cron.

Since I posted, I have "flushed the language cache" -- which I learned about from another post here I think. Neat trick ;). I still intermittently received the memory error, but have also since begun running cron once per hour (rather than twice a day) -- and since then I haven't received the error at all.

--
Some of the posts can have a hundred, two hundred or more lines of code to highlight.

Actionscript:
http://flashpanos.com/content/open-source-flash-pano-viewer-based-pv3d-u...

XML:
http://flashpanos.com/content/progress

Thanks again, and

Cheers,

Patrick

[edit: whoops -- here you go:
"GeSHi library version 1.0.7.22 detected"]

soxofaan’s picture

soxofaan commented
Title: Fatal error on cron run (allowed memory size exhausted) » Fatal error on cron run with Subscriptions module (allowed memory size exhausted)

I don't think flushing the language cache would change something for you, that's just needed when you change something in the language definition files.

What does that subscriptions module do on your site? Emailing listings of nodes/comments to users or something?
If there are a lot of nodes and comments to be sent and the subscriptions module rerenders each of them instead of fetching them from the filter cache, it's not unlikely that you get an exhausted memory.
That would also explain why using a more frequent cron results in less errors because less nodes have to be rendered each cron run.

So I think that a more frequent cron is the workaround here.

cheathamlane’s picture

cheathamlane commented

Hi there:

OK! -- Understood on all points.

Yes: Subscriptions sends out email notification of new posts or comments, to subscribed users.

I'd been keeping cron to twice daily, but site traffic is picking up. More crons it is!

Thanks again,

Patrick

soxofaan’s picture

soxofaan commented

Yes: Subscriptions sends out email notification of new posts or comments, to subscribed users.

Just to be sure: does subscriptions send entire bodies of those nodes and comments or just a list of links?

cheathamlane’s picture

cheathamlane commented

Currently Subscriptions sends a list of links and subject lines.

I have been narrowing this down, but am still stumped. I think it may ultimately _not_ be a GeSHi Filter specific issue, as I'm not receiving any more errors related to GeSHi.

I now get a "cron run failed" or "...is stuck" error daily; Including/excluding modules finally showed it to be a site indexing issue (search module). When I disable search and the site isn't indexed per cron run, I get no errors. When search is enabled, the site is indexed incrementally (10 items per cron run). When the index gets down to 26 items left, cron begins failing.

:(

Not an issue for this thread anymore!

Thanks,

Patrick

soxofaan’s picture

soxofaan commented
Title: Fatal error on cron run with Subscriptions module (allowed memory size exhausted) » Fatal error on cron run (probably due to search indexing)

Do you have any idea on which nodes the search indexing is choking?

cheathamlane’s picture

cheathamlane commented

Hi there:

Thanks for your continued interest...

I'm not sure how to tell which posts may be causing search indexing to choke (and don't know how to get it to show up in the error logs).

A few posts suddenly began causing "500 internal server error"; this was just after beginning to use GeSHi filter (though that may just be timing and not a real cause/effect relationship). I was able to go into edit mode, via Admin:content, and grabbed all their text.

On a lark, I used BBEdit's "zap gremlins" function, and a few non-English characters popped up. I removed/replaced those and republished the pages and all worked fine. One of these is a fairly long post, but I don't know how to tell if it's length which causes search indexing to choke.

?

Cheers,

Patrick

cheathamlane’s picture

cheathamlane commented
Title: Fatal error on cron run (probably due to search indexing) » Nodes, coments, pages etc return "500 Internal server error" when including <code /> wrapped content

Hi again:

:)

Have narrowed things down a bit... When a comment or post includes any "<code />" highlighted content which contains an ampersand or question mark, the site generally fails to display it (in favor of an internal server error).

When I go in as admin and edit the said comment or page to use "<%" style wrapping, things work as expected.

The site gets a lot of XML, HTML, Javascript, Actionscript code posted.

Thoughts?

http://flashpanos.com
or an exemplar which I fixed today:
http://flashpanos.com/content/how-load-panos-using-common-xml

Cheers,

Patrick

boombatower’s picture

boombatower commented
Status: Active » Closed (cannot reproduce)

Please re-open if relevant to recent version.