use drupal_static instead of static $cache

This patch is out of date and needs calls to drupal_static() to be by reference:

$processed = drupal_static(__FUNCTION__, array(), $reset);

Should be (note the &):

$processed = &drupal_static(__FUNCTION__, array(), $reset);

But definitely +1 for this - features is a pig for memory, so moving to the static caching system is a good step away to being better able to manage memory usage (via resets).

We have this running in production for months now.

Don't see this code in the features codebase. Has this patch been committed at all?

Issue #2143765: features_modules_enabled() doesn't work when features_load_feature cache doesn't include the feature got me here. Have the same issue with 7.x-2.2

Seems like it was closed before actual commit was done. Reverting status back to "Reviewed & tested by the community"

It looks like this may need a re-roll as well.

@joelpittet and @Taran2L I am pretty sure that this has been committed. I tried a reroll just now and ended up with an empty diff. So setting back to Fixed. If you disagree, please reopen again.

@lsolesen I think you are correct, just the committed code is just slightly different than the patch for the resetting approach and no commit hash showed up in the issue queue.

Hi @all,

Sorry for the confusion: I've had a false impression, that my issue is cache-related.

Actually, it's related to the fact, that Features module fails to include files when module(s) are being enabled.

See more #2143765-6: features_modules_enabled() doesn't work when features_load_feature cache doesn't include the feature