How to Handle Cases Where There is Not Enough Memory?
davegan - September 8, 2008 - 21:33
| Project: | Drupal For Firebug |
| Version: | 5.x-1.1 |
| Component: | Code |
| Category: | bug report |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Some pages, such as the modules administration page, receives a max_allowed_packet error when that mysql setting is equal to 1M. Changing this to 2M in the mysql settings file seems to do the trick, but on a shared hosting account that wouldn't be possible.
#1
So the general issue here is that Drupal for Firebug stores in memory a lot of information about the users + nodes + forms + views + whatever that is happening. This can overwhelm a shared hosting environment (or deployment with limited memory) and cause errors. A few possible options:
1.) require more memory. its often just changing a few settings in settings.php to make it all work
2.) storing data in the database for each item an custom calling it out of hte database when requested by drupal for firebug
3.) providing settings to allow user to turn off some of the features (like not store node information)
4.) cap the number of objects that will be displayed to X number
any perference?
#2
Its probably best to require more memory and I have updated the README to explain how to add more memory.
#3
Automatically closed -- issue fixed for 2 weeks with no activity.