After updating Drupal to 6.10 I get the following error in many of my views:
Fatal error: Allowed memory size of 31457280 bytes exhausted (tried to allocate 41 bytes) in /home/www/[...]/htdocs/modules/views/modules/user.views.inc on line 382
The error can simply be reproduced after overriding the tracker and going to /tracker.
Installed modules:
Drupal 6.10
ACL 6.x-1.0-beta4
Bbcode 6.x-1.2
Calendar 6.x-2.0-rc6
Content Construction Kit (CCK) 6.x-2.1
Date 6.x-2.0-rc6
DB Maintenance 6.x-1.1
Flatcomments 6.x-1.0
Google Custom Search Engine 6.x-1.2
Mollom 6.x-1.7
Pathauto 6.x-1.1
Privatemsg 6.x-1.0-rc2
Quote 6.x-1.1-beta2
Signatures for Forums 6.x-1.0
Smileys 6.x-1.0-alpha5
Taxonomy Access Control 6.x-1.x-dev (2008-Aug-28)
Token 6.x-1.11
Views 6.x-2.3
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | bug_384036.view.txt | 1.47 KB | softrusher |
Comments
Comment #1
merlinofchaos commentedI guess you need to up your memory limit. It's easy to find by googling that error message.
Comment #2
softrusher commented32MB memory limit is quite high for a shared server. Nonetheless I narrowed my problem down:
Even the most basic view gives me an error but only if using the table layout.
Example as LIST: (Limit 10)
The same query as a table layout gives me an error about my 32MB memory limit. Switching themes did not help. View is attached.
This might be something to look into so I will open the bug once more. If you close it again I will let it be. If you need more info from me don't hesitate to write here, I will do what I can to help.
Comment #3
softrusher commentedComment #4
Aiiane commentedI've run into this same issue, running 6.10 and Views results in Fatal Errors constantly.
Comment #5
Patrick Nelson commentedI'm running into the same error consistently on a site that used to work fine on 6.9 and has received nothing but an upgrade to 6.10. Nothing has changed in the hosting environment either and it has a large shared hosting environment memory of 256Mb.
Comment #6
dawehnerthis is still not fixable
the problem is your hosting, sry
Comment #7
merlinofchaos commentedHm. IF it won't run in 256M there is a problem. Though if it's the 6.9 -> 6.10 update that's causing it I am not sure Views is going to turn out to be the culprit. I won't know until I can reproduce it and hunt down what's consuming so much memory, though.
Comment #8
esmerel commentedIs this still an issue, nobody's complained in a year about it.
Comment #9
esmerel commented