Thought I'd report this to see if others have issue

Used with Views 7.x-3.5, OG 7.2x and Core 7.15 -

when View - OG Extras group members at /node/%/members is enabled, I cannot update the database at /update.php without a Fatal error: Allowed memory error, even with 2.5GB of memory allotted and a 300 sec execution time in php.ini. Disable the view and DB updates with 500MB memory and 30sec exec time no problem. Could be my OG configuration but no other problems of note.

Comments

eojthebrave’s picture

eojthebrave
he/him
Primary language English
Location Minneapolis, MN
CreditAttribution: eojthebrave commented

I've not been able to replicate this problem. I tried to, but updating a site that had 50 groups each w/ 25 posts in them went off without a hitch. I tried in both the UI w/ update.php and w/ drush. I've tried it while updating core, og, and views together and individually.

Could you tell me what you where trying to update when you experienced this problem? Which module had database updates that it needed to run? Thanks.

metakel’s picture

metakel CreditAttribution: metakel commented

I have the same problem with 7.x-1.1+5-dev.

Once I enabled the module I cannot access the site.

Sometimes it shows WSOD (white screen of death), sometimes it shows memory exhaust, sometimes it says:

Fatal error: Class 'MergeQuery_mysql' not found in /path/to/drupal/includes/database/database.inc on line 826

(the line numbers above sometimes change)

Even I set the PHP memory limit to 1GB, I still got the error. Once I disable the module, the problem is gone.

No error is logged by the error log of Drupal. Maybe the problem is triggered before database is invoked.

metakel’s picture

metakel CreditAttribution: metakel commented

Tried again in a brand new installation and the memory still exhaust even I set it to 1GB.

Not even a single Basic Page can be loaded. And the problem gone once I disable the module.

mariusm’s picture

mariusm CreditAttribution: mariusm commented

Hello,

Used with Views 7.x-3.5, OG 7.2x and Core 7.17

I have same isue.

The problem gone once I disable the view "OG Extras content"

eojthebrave’s picture

eojthebrave
he/him
Primary language English
Location Minneapolis, MN
CreditAttribution: eojthebrave commented
Status: Needs review » Active

Could someone please help by providing a set of steps to reproduce this problem. I've still not been able to reproduce it myself. That, or if someone is willing to share a DB dump + zip of a site that is exhibiting these problems that would be super helpful. It can be stripped of all personal information as long as it will allow me to see this issue in action. Get in touch w/ me via my contact form if you can share this.