Fatal error: Out of memory .... database.mysqli.inc or database.inc

this is not a RDF module related issue. if the status report page says the PHP memory_limit is still at 64MB, then the directive in .htaccess didn't work. your host might have disabled it. Try to specify it in settings.php. see http://drupal.org/node/207036

can you paste the error message you got in the error log please? also file an issue with the activity module to see if you can get some help there. have you tried with activity-6.x-2.x-dev?

leaving this issue open for a bit until you figure out which module is causing this.

I am getting the same basic problem. I can reproduce it at will now, at least on my site, but I have not tried on a clean site. I posted about it in the forums here. The memory limit error seems to be a red herring; every reference I've seen to this kind of problem with one of the .inc files has not been resolved, even by giving massive amounts of memory to PHP. (For the record, I'm on shared hosting and my limit is 32 MB.)

I'm using Acquia Drupal 1.2.4. I was previously using version 1.2.3 and did not experience the problem with it.

I have been using Calais version 6.x-2.2, with both the Calais and Calais API modules enabled. They require RDF. I have not previously had problems with them.

I have been using RDF 6.x-1.0-alpha5 (and did not have a problem with it) but upgraded to RDF 6.x-1.0-alpha6 (at the suggestion of Update Status) at the same time as Acquia Drupal 1.2.4. I also added in the latest ARC 2 library at the same time. The Calais module version did not change. I can tell all this because my site is under version control with Mercurial and I track every module change with a revision in the repository.

With RDF 6.x-1.0-alpha6 enabled, every time I enable both the Calais and Calais API 6.x-2.2 modules (both of which are needed for Calais to work), my site fails with a fatal error as described by the OP above when loading the Modules List admin page. If I revert my site back to its Acquia Drupal 1.2.3 state, I can load the Modules List to enable/disable modules, and then change my site back to the newer version. (I'm just swapping site directories around by renaming them.)

I don't know whether this problem is in RDF or OpenCalais or Acquia Drupal or even somewhere else. I'd be happy to do more troubleshooting and provide more details if you have any pointers on what to do to narrow it down. However, I can tell you that the steps above reproduce 100% on my Acquia Drupal site. HTH, and let me know if I can provide more information (although simple steps/walkthroughs, or links to them, would be appreciated).

hi.. I'm very new to Drupal . i faced this memory error message in /includes/database.mysqli.inc on line 303 .i noticed one thing that that problem can be solved by un installing or deleting some modules which are already in the module directory like open id (but i don't know it why).
it is also noticed that same type modules make problems.!it is like 'fckeditor' can be installed after the removal of 'widgeeditor' and etc.
expect that these illusions will meet the problem.

I can't say the problem lies with this module alone, but using it in conjunction with other memory intensive modules (devel+trace for example) has me hitting my memory limit of 128MB.

I want to be clear that I'm not blaming this module exclusively, I just happened to be able to reproduce my particular problem reliably when I enable it with OpenCalais. I'm completely open to the possibility that all of my other modules are also contributing, but I had roughly the same module load — and none of the memory problems — before I upgraded to 6.x-1.0-alpha6 from 6.x-1.0-alpha5.

I'll try to post a list of the modules I am loading later because that may help with the reproduction scenario. I'm not loading the Devel module.

So I upped php's memory limit to 256MB...problem solved! No seriously though - I'd love to contribute some information on this one - I'll see what I can get out of the logs.

The module page loads all the modules (installed or not) which tends to consume more memory. Is it the only page you guys are having problem with?

Also you could use devel and enable the memory consumption which will be displayed at the bottom of each page. With that you could try to see which module is taking too much memory by enabling one module at a time.

I had sporadic problems with other pages beyond the Module List, but hadn't narrowed them down as I have with the Module List. I'll see about the Devel module (when I mentioned not loading it earlier, I meant I wasn't loading it at the time of the problem and offhand, I don't know that I have it installed), as well as listing out my active and inactive modules.

Would deactivated themes also have an impact similar to installed but inactive modules? Just curious, because if so, I'll list out those, as well.

I don't think themes would have as much impact as modules. it would affect the themes page only.

I tried updating to alpha7 and get the same result — actually, a little bit worse, as it initially wouldn't load the main Admin page. If I just revert to alpha5 (which I did do, since I'm using Mercurial to check in versions), I still get the out of memory error. And the database has changed between alpha5 and 7 so that downgrade is probably not something I'd want to leave in place, anyway.

Is there a good way that I can list/export all the modules I have, and which ones are activated? Since I had to turn off RDF and Calais through PHPMyAdmin, I found that I could export the results of the query to find all the modules (as covered in the Drupal Handbook). However, that lists ~257 modules and themes (!!!), and looks like it includes modules I used/tried out with my Drupal 5 installation that are no longer present today. (I upgraded from Drupal 5 to Acquia Drupal.) I'd paste that here, but it just seems silly since it won't even reflect the modules I have installed but deactivated. It also seems to list every little submodule and content type and so on.

I'm going to try Devel next, to see if I can find out more about what's taking up memory when loading the Modules List.

hi...
this problem can be solved by editting the php.ini file and settings.php.

1.In your php.ini file, include a line that reads: memory_limit = 16M.
2 …in your settings.php file, include a line that reads:

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

drupal already warns about this problem
check out
http://drupal.org/node/36628 check it out .....!!!
One more thing.....
i used '30M' in the place of '16M' to get
the problem solved...

I’m on shared hosting and beyond logging a support request to up my limit, I have little control over the actual PHP memory limit value. Granted, shared hosting may not be ideal for running lots of modules or certain selections of modules. However, it has worked until I add this one into the mix. The only place I’m having consistent problems is on the Modules List page when RDF + OpenCalais are enabled, as above. These are two modules that would be of interest to people wanting to run Drupal and experiment with its semantic Web capabilities.

However, as long as I’m mentioning that, I did run the Devel module to get a baseline of my Modules List page before RDF + OpenCalais are enabled.

Memory usage:
Memory used at: devel_init()=1.27 MB, devel_shutdown()=25.9 MB.

I just re-enabled only RDF + Calais + Calais API (in addition to my previously-enabled module set) and got this when loading /admin/build/modules:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 1141051 bytes) in /home/my_site/public_html/my_site/includes/database.mysql.inc on line 301
Memory usage:

Memory used at: devel_init()=1.27 MB, devel_shutdown()=29.87 MB.

I’ll go back and turn the three modules off, and then re-enable them one at a time (now that I’ve re-read the thread in the process of writing this note).

I disabled RDF + Calais + Calais API from PHPMyAdmin, and successfully re-loaded my Modules List page. Then I enabled only RDF. Immediately, I got the following error:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 1273570 bytes) in /home/my_site/public_html/my_site/includes/database.mysql-common.inc on line 41
Memory usage:

Memory used at: devel_init()=1.27 MB, devel_shutdown()=29.5 MB.

Since RDF is a prerequisite for the Calais modules, I’m not sure I can proceed.

Ugh, my update was lost. Summary: I enabled Calais and Calais API individually using PHPMyAdmin, and each increased memory usage to about 26 MB. Therefore, it looks as if the RDF module is the big culprit, taking up an additional 3.6 MB when loading the Modules List page.

This may be warranted but it is a large chunk for my site on shared hosting with my other regular modules. RDF is also a prerequisite for the OpenCalais integration, which means I can't really run either with my current module load, unless I can get my host to increase the allowed PHP memory limit.

Is it likely the memory usage of this module can be reduced, at least in the instance where the modules list is loaded by an administrator?

Hy

I have the same error (Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 777093 bytes) in /homez.143/altbzh/www/drupal/includes/database.mysqli.inc on line 303) and I don't use Calais .... The admin of my hosting server (OVH) tells me it's not a PhP memory problem but a database one. ( I use 7 MB and the limit memory of my data base is 40MB). It's always in the command admin>site building>modules and only in this command.

I am not a programmer but it's always the same error is in the "return" of the following fonction :

function db_encode_blob($data) {
global $active_db;
return "'". mysqli_real_escape_string($active_db, $data) ."'";
}

Is-it possible to include some lines of PhP to trace the bug ?

Difficult to understand that Drupal need so many bytes !

Have a good day

Alain

#414250: Fatal error: Allowed memory size of 33554432 bytes is comming in friendlist module #1

loading the modules page requires more memory than the usual page, that's well know and there isn't much we can do about it. there is a documentation page on how to increase the PHP memory limit. Still, I cannot reproduce this even by decrease my php memory limit with the latest version of the RDF and Open Calais (plus a whole pile of other module). Could you poste a list of your modules (enabled/disabled) and the version of PHP and MySQL please?

Make sure that after increased your memory, memory has been increased in your PHP configuration.
You can check that by going to: admin/reports/status (Administer -> Reports -> Status Report).
Sometimes even you increase your limit, limit is still not increased in example on Servage hosting.

I'm running into this problem as well, though I'm not even running RDF. In fact, in my case a few different variables are in play that I thought I'd list in this thread to add to the data points:

1. I receive the error not only when trying to access the modules page, but also when attempting to save a View.

2. I have approx. 70 CCK content types. It appears that when I'm in the 40-45 CCK content type range, I don't receive these errors, but when I increase past that, the errors begin. A few more than 45 and I see the error when I try to load the modules page. Add more content types, and I can no longer save a view. Add even more and the errors begin to show up in more admin functions.

Again, my issue has nothing to do with RDF, but it seems like this is the most active thread on this topic.

I have the same error when i flush the cache by admin menu module. I resolved the problem sending the php.ini file to folder containing the file described in error. Then flushed the cache.

Eg: Fatal error: Out of memory (allocated 77332480) (tried to allocate 80 bytes) in /home/yoursite/public_html/includes/menu.inc on line 966

Place the php.ini with greater memory limit on /home/yoursite/public_html/includes/

I had a similar problem with other modules. I installed Token Tweaks and changed the depth of token tree and it fixed my problem.