I've had my site running on drupal 6 (migrated from d5) for about a week and it has crashed twice due to it running out of memory.

I recently found out that the problem is the pageroute row in cache database table keeps growing bigger every time a user page or certain other content types are loaded. The site keeps reading it, adding to it, and then inserting new content with all the old content. If I don't clear the cache after a day or two, the cache can become huge, which leads to major memory problems.

I talked to thomjjames, who said the problem in question is likely the load function in pageroute.route.inc.

If anyone can help further narrow down the issue and/or confirm if it's also happening on your end, it'd be a really big help. I love the module and it's become a crucial aspect of my site (thanks to profilesetup). I'm not a Drupal developer so I'm usually relying on paid assistance for urgent issues on my end. If I get any help I'll update the post.

Comments

thomjjames’s picture

I can confirm that this bug exists.

Tom

drm’s picture

As well here. My site is not a D5 upgrade. I'm using beta4. I've had to tell my client to clear their cache manually on a regular basis since cron is not doing it. Once the crash occurs, you have to go into the database and delete that row in the cache table.

sepgil’s picture

That problem should be fixed now(in the latest dev version). I'll release a new Beta tomorrow.

sepgil’s picture

Status: Active » Fixed
davej’s picture

Same issue here, completely incapacitated a server. Just applied the fix, the cache size & memory usage seem stable so far.

Dave

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

dbirider’s picture

I installed the latest dev. My site's moving much faster now and the cache issue is gone. Thanks!

joseonate’s picture

I can confirm as well on both accounts. The average memory load to render a page was increasing by about 0.15MB per page load until it crashed the site. I installed the 2009-Dec-23 dev version and the problem seems to be fixed.

mrfelton’s picture

I just got hit by this problem. I'm interested to know how you managed to track this down to the pageroute entry in the cache table as the cause... I have been trying to trace this for a while.