After Module updates got "Warning: require_once() " I am using Drupal -7 and my website is on cloud(not local host).
This is NOT a multi site and using Omegasubtheme.

I have just updated workbench Moderation module from 1.3 to 1.4 and have also added Workbench Media module(7.x-1.1) to my dev. site.
After running update script, I got bunch of errors on my site. So, I again moved Worbench Moderation Module from 1.4 to 1.3.

Devel Generate and Devel Node Access Modules were enabled in my site and I made those module disabled.

After that, I got these errors so I made them enabled again. 
I found this thread but, this is for database.inc for memory allocation error message in database.inc.

Devel Module



Can anyone help me how to get rid of these errors?

Errors which I got on front page:


  Warning: require_once() [function.require-once]: Unable to allocate
  memory for pool. in _registry_check_code() (line 3177 of
  /docroot/includes/bootstrap.inc).
      Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in _registry_check_code() (line 3177 of
  /docroot/includes/bootstrap.inc).




Errors on available updates module page:


Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in menu_execute_active_handler() (line 515

  
  of /docroot/includes/menu.inc).
      Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in module_load_include() (line 330 of
  /docroot/includes/module.inc).
It would be interesting to see if your problems could be related to the "memory limit", which might not be high enough (anymore), especially because of the "... have also added Workbench Media module ...".

Assuming this is NOT a multi site, consider editing your /sites/default/settings.php, and change the line to set the memory limit. If it is a multi site, then edit the settings.php file related to the site where you are experiencing the problem.

That line in settings.php should look similar to this:

ini_set('memory_limit', '100M');


The '100M' in it might be some other number. Whatever the number is, try to increase it with like 50%, or maybe even double it to see what happens after you do so (of course do not forget to save the file after increasing that number).

Another possibility that you may want to verify, is to "perform a clear cache" (it doesn't hurt, and occasionally helps solving various issues).

Curious to hear if that helps somehow ...