Posted by iantresman on May 26, 2009 at 5:56pm
Jump to:
| Project: | Custom Pagers |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
I've successfully set-up a custom pager. But on entering Views 6.x-3.x-dev, and adding a new view, after entering the new View name and description, and selecting the View type as Node, pressing Next gives the error message:
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 35 bytes) in /my-path/public_html/sites/all/modules/custom_pagers/custom_pagers.module on line 231.
I've already increased my PHP memory to 32Mb by adding a line to my .htaccess file.
This issue could be related to the post "custom pagers eating a ton of memory"
Comments
#1
On increasing the PHP memory to 48M, I get the error message:
Fatal error: Allowed memory size of 50331648 bytes exhausted (tried to allocate 35 bytes) in /my-path/public_html/sites/all/modules/custom_pagers/views/custom_pagers_plugin_style_php_array.inc on line 18Increasing the PHP memory to 64M resolves the issue, and I get no error message.
#2
Still appears to be a problem, on visiting my home page, I get the error message:
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 4 bytes) in /my-path/public_html/includes/database.mysqli.inc on line 144On removing the Custom Pager module, the error message disappears.
#3
Yep, this is happening to me. Sadly, I'm on dreamhost so I can't raise my memlimit - dreamhost just kills my php processes automatically when they take up too much memory, which means I end up with 404s on my views when I try to return too many nodes that have custom pagers in them. I'm pretty sure it's custom pagers that's doing it, I've tried disabling all my other module and disabling custom pagers is the only thing that fixes it. Even aggressive caching doesn't seem to help that much. Would love a way to keep custom pagers from loading on certain node views. :(
#4
Views 3 is an under-development version that is shifting and changing rapidly. I'm not testing Custom Pagers against it, and I can't make any promises about how it works with that version.
Also, how many nodes (roughly) are being returned? With very large pager sets it can be a problem. So far, I haven't found a clean way around that.
#5
This issue touch me too. There are about 50K nodes on my site. And every time when a node is opening it takes a lot of memory to load array with all node's ids for custom pager module.
I think some workaround may be used here. Add some filters or arguments to your views which decreese resulting quantity of nodes.
#6
This tip worked for me. I added on my view at Arguments :
+ Node: Created day - > Provide default argument -> Current node's creation time
I'is not perfect but this works for me.
-----------
ministiri
#7
Had similar problem with custom pagers and boost
http://drupal.org/node/936422#comment-3634140
#8
The tricky bit is that there's no good way to support the flexibility that's currently there (create any view, use Custom Pagers to step through it) without either 1) forcing all the nids to be loaded, or 2) a dramatic rewrite that dynamically tweaks the View before it's executed to load only the nids it requires. The latter is better in the long term but would almost certainly sacrifice compatibility with any sort that lacks a corresponding filter handler. The former works for small sets of nodes (hundreds, say) but dies on large sets (many thousands) in memory-constrained situations.
Thoughts? Anyone?
#9
Why can't we have view load just first next node to current one with settings we want? If views is not up to that task, lets than have custom query/function that takes date, node type, sort type etc
#10
Most Drupal sites require 128M+.
Closing year old issue, re-open if needed.