Flexer

No problem; 4 weeks no response from OP, I thought it would be good to revive.

In any case it seems that upping the memory for the account took care of the error. Although 64M should be fine; in this case 96M was required. Just wondering if the memory requirements for Jetpack have changed? Specifically during the authentication process.

Over and out
Daveed

Hi,

I will try to revive this post as I am running into the same issue:
Wordpress 4.1.1 – some plugins but no caching ones.

Install JetPack – no problem
Connect to WordPress.com: Fatal PHP Error;

Tried this twice: both times renaming plugins/jetpack resolves the issue. Both time the error is the following:(From cpanel Error Log)

Haven’t noticed the issue in older installs with Jetpack connected; But I will not update Jetpack untill I hear back.

[Tue Feb 24 06:02:23.411084 2015] … PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 30720 bytes) in /public_html/wp-includes/class-IXR.php on line 1056

[Tue Feb 24 05:33:17.088940 2015] … PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 30720 bytes) in /public_html/wp-includes/class-IXR.php on line 331

Thank you
Daveed

Just went live- and the error is gone.
Thanks again for your lovely plugin.

Is there a PayPal I can buy you a beer or a fruit juice ??
Feel free to email me directly at [email protected]

Daveed

Nope no caching plugin installed.
> Twentytwelve Child
> Advanced Custom Fields Pro
> Akismet
> Jetpack by WordPress.com (no caching)
> Limit Login Attempts
> Under Construction (site is not live)

Could it be as it’s hidden behind a coming soon page?
Going live today- can see then.

Thanks
Daveed

EDIT: Previous version did not throw this error; and nothing else changed except a new version of Jetpack I believe.

Yes, this just happened to a client site as well.

Cool that worked.

I previously opened a support ticket with JetPack and I’ll update them with your solution turtlepod. It should go into future code so your solution does not get erased when JP gets an update.

Thanks
Daveed

The theme was twentytwelve child
It was while embedding the Jetpack form. If you Google the error it looks like it is other Jetpack forms.

Flexer

Thanks for the fix @webstract Marketing. If you google the error you get tons of sites, must be a 3.9 bug.

Wouldn’t this fix be erased whenever we update wordpress? I was using TwentyTwelve and got this issue. Alterantively perhaps it will be fixed in the next update to 3.9.