I am developing a site in Drupal 8.4.4 in Acquia Dev Desktop 2 in Windows 10 with PHP 7.1.11 .
I would like to update to Drupal 8.5.0-beta1 (rather than waiting for the stable release) to see if it solves this issue.
After installing Drupal 8.5.0-beta1, when I run update.php, I see that there are 11 pending updates:
When I click "Apply pending updates", I get a white screen with "Fatal error: Out of memory" errors. I have gradually increased "memory_limit" in C:\Program Files (x86)\DevDesktop\php7_1\php.ini and now, with it set at -1 (unlimited), I have this type of error message:
Fatal error: Out of memory (allocated 828375040) (tried to allocate 4096 bytes) in C:\Users\Nick\Sites\devdesktop\drupal\core\lib\Drupal\Component\Annotation\Plugin\Discovery\AnnotatedClassDiscovery.php on line 129
What can I do next to troubleshoot this?
Comment | File | Size | Author |
---|---|---|---|
update-8pt4pt4-to-8pt5beta1.png | 35.61 KB | Nick Hope |
Comments
Comment #2
cilefen CreditAttribution: cilefen as a volunteer commentedComment #3
cilefen CreditAttribution: cilefen as a volunteer commentedThis could be related to #1596472: Replace hard coded static cache of entities with cache backends but I’m just guessing based on the data given.
Comment #4
Berdir> I would like to update to Drupal 8.5.0-beta1 (rather than waiting for the stable release) to see if it solves this issue.
It makes sense of course to do that on a test site, but I've seen a bunch of people updating to 8.5.0 alpha on their production site and then ended up with bugs that broke their site. So just saying, be careful.
Updates, especially resaving all config/views does need a large amount of memory, I'v seen a few times already that for example 256MB was not enough but I've never needed more than 512MB, also on very large sites.
So either you have even more views than my sites, something else might be the problem. Also strange that it happens during annotation discovery.
Are you sure that you edited the right php.ini? Check admin/reports/status/php.
Can you enable xdebug, make sure that you get a full stacktrace in case of a fatal error and report that? Maybe you have some kind of loop that will eventually die on memory. xdebug will actually also change that and report a recursion fatal error.
Does this happen always? E.g. on drush, you end up doing multiple cache clears in a row and I've seen that being too much, so a second run might then go through.
Comment #5
Nick Hope CreditAttribution: Nick Hope commentedThank you for the replies. I will get back to you with the information as soon as possible. Unfortunately for the time being I have lost access to my development site.
Comment #6
Nick Hope CreditAttribution: Nick Hope commentedI have now successfully managed to update to 8.5.0-beta1 and do a clean database update.php using 1024M memory, and since then things seem to be working OK.
I did have a lot of unused Views and modules, so I cleared as many of them out as I could. That may have helped.
I also had errors related to Media Entity Flickr, as shown below, so I updated from 8.x-1.1 to 8.x-4.0-alpha4, and the message didn't return.
Comment #7
cilefen CreditAttribution: cilefen as a volunteer commentedI’m glad to hear it!
Comment #8
Nick Hope CreditAttribution: Nick Hope commented