Fatal error: Allowed memory size

Strange, that's as part of a query, doesn't seem like something token specific.

It would help a lot if you could enable verbose error display, so you can see the full backtrace of that error. You could also try our past logging project to get a better error with backtrace: http://drupal.org/project/past

Token has known memory issues, already was a big issue in 7.x as you said. But that's mostly about the token UI, the only real solution there is to build a UI that uses ajax lazy loading to expand the tree and not build/load everything upfront.

PS: You probably heard of it, but https://www.drupal.org/project/paragraphs can often result in fewer content types and more flexibility, as structures can be put together in more flexible ways. But that depends a lot on what you have need on a site. Another option is defining custom entity types, especially when a lot of what node does by default is not needed (like showing on a page with alias/menu/... integration or if revisions and/or translations aren't needed).

Hm, that's not really useful yet. Since it's a fatal error, can you see more information in /admin/reports/dblog? past afaik currently has a bug with that on PHP7.

Can you provide more information on when it happens? Does it only happen when you actually want to look at a token UI or also on other pages?

Hi Guys,

Here's a little more info. Maybe this could offer some additional thought points for troubleshooting:

Based on the Business Rules interaction instructions, they suggest a parent child type workflow as in: create a condition, create an action, then create a rule and tag your existing condition and action.

Just to try to offer some further info... the error will fire when following these steps:

1: Go to /admin/config/workflow/business_rules/collection
2: Go to /admin/config/workflow/business_rules/action/add
3: Select an action from the dropdown (i tried Show a Message)
4: Click the Continue button - this is where the memory error will show:

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 152146117 bytes) in /srv/bindings/611d45201f254779b7491001c71e7441/code/core/lib/Drupal/Core/Database/Statement.php on line 59

*Note: The same error will fire if you try to add a condition first.

I checked the watchdog and nothing is posted to it regarding this error. I was expecting something to show there. That's what brought me to the guess that the admin UI might be having a memory issue due to the field count (my guess leaning towards tokens and ajax). But I am totally guessing there as this is not my forte. I'm just going by D7 situations that I recall.

Is there anything else I can do to help troubleshoot? Please feel free.

@cielo & @jeppy64,
Came across this thread while contemplating use of Business Rules for a client project. I concur with jeppy64 that without a stacktrace the likely cause is the large amount of tokens being passed by the AJAX and exacerbated I'm guessing due to something related to the explanation listed under "Why is the AJAX request so large?" on #956186: Allow AJAX to use GET requests. If this is the case, you might be able to do a quick Token Tweak test of your own by changing TOKEN_MAX_DEPTH on line 11 of token.module (http://cgit.drupalcode.org/token/tree/token.module?id=fb05b225ee0c93835f...) from:
define('TOKEN_MAX_DEPTH', 9);
to
define('TOKEN_MAX_DEPTH', 2);
or
define('TOKEN_MAX_DEPTH', 3);

If it works, then you can create a patch to manage it until Token Tweaks is ported to Drupal 8 for users with conditions such as yours.

P.S. You may want to either lockdown your pantheon dev site with HTTP Basic Authentication or editing the Referrer and Location links from Comment #4 above to keep Google from picking up on it and making it available in public search results.

I am having this issue too. @C13L0, have you all tried anything new? Did you try the TOKEN_MAX_DEPTH tweak at all?

Thanks,
Charles

@C13L0 any updates on a resolution path?

I tried the TOKEN_MAX_DEPTH tweaks, without any effect.

thanks in advance for sharing...

D

I have this problem when I use drush cim

Same problem happens us using Drupal 7 using Token for a large site which has lots of content types, fields, vocabularies, and contrib modules.

Enabling fast_token_browser module solved the issue.

Hope it helps someone.

Regards!

Thanks @sircosta

On a Drupal 8 site, I am having the same issue described in #6. I get the following error when trying to edit any part of an existing business rule:

Fatal error: Allowed memory size of #### bytes exhausted (tried to allocate ##### bytes) in .../web/core/lib/Drupal/Core/Database/Statement.php on line 59

I looked for a way to edit the token.module as described in #7, not seeing the code "TOKEN_MAX_DEPTH"; perhaps that suggestion is for Drupal 7?

Any advice would be greatly appreciated.

Thank you!

Any updates on this one?

Hi! Any update on this? Thanks!

Hi,

Is there anyone who can try to check and fix ? without that fix the business rules awesome module is not useful at all as tokens have to be enabled.