Skip to:

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#1982 closed defect (bug) (fixed)

Fatal error allowed memory size

Reported by: anointed Owned by:
Milestone: 2.2 Priority: normal
Severity: normal Version: 2.1
Component: General Keywords: reporter-feedback


Something changed with bbPress 1.7 in the last few days.

Now, when I visit the dashboard, I get the following error:

mod_fcgid: stderr: PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 80 bytes) in /home/ on line 1542, referer:

Now I can get to the dashboard, it dies when it hits the 'now happening in forums' box. I can also get to the forums front end and the rest of the admin just fine.

If I deactivate bbPress then everything is perfect. This was NOT happening last week when I installed bbPress 1.7, in fact it was working great.

I took a few days off, didn't touch the site, other than that the svn is on a nightly cron to update.

I had a number of site members tell me that all of the sudden they could not post, which is how I found the error.

When I went into the site originally and went to the admin, I would get a white screen. So I renamed the plugins folder which killed all plugins. I was then able to get back into the admin.

It was when I turn on bbPress that this error comes up. Now I don't get the white screen, but do have the errors.

I am running WordPress 3.5beta2 and buddyPress 1.7 both also nightly cron.

Change History (5)

#1 @johnjamesjacoby
9 years ago

There is no bbPress 1.7. BuddyPress does not have a 'happening now in forums' metabox.

Do you mean bbPress trunk?

If so, it's probably the call to get_users().

#2 @johnjamesjacoby
9 years ago

  • Keywords reporter-feedback added

#3 @johnjamesjacoby
9 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [4254]) bbp_get_total_users():

  • Use count_users() instead of get_users().
  • Fixes #1982, #1984.

#4 @johnjamesjacoby
9 years ago

  • Milestone changed from Awaiting Review to 2.2

#5 @anointed
9 years ago

As I said in the other ticket, I believe this is now fixed. I will keep an eye on my server error logs over the next couple of days and report any new out of memory errors should they happen again. It does seem much much better now

Note: See TracTickets for help on using tickets.