Hi,
first thanks for all your work on this module!
I currently installed views-module 6.x-2.0-alpha3 and tried to set up a new view.
After submitting the form (/admin/build/views/add) there was an error about exhausting php's allowed Memory..
I tried to increase it a little (up to 512MB) but that was no solution.
Also i tried to select another 'view type' but this error happened with all types.
Hope you got an idea about this..
thanx ib0t
---
My Installation contains the following modules:
Drupal core
Drupal 6.1
Includes: Block, Blog, Color, Comment, Contact, Content translation, Database logging, Filter, Garland, Help, Locale, Menu, Node, Path, System, Taxonomy, Update status, Upload, User
Modules
Devel 6.x-1.7
DHTML Menu 6.x-1.02
Image 6.x-1.x-dev (2008-Mar-03)
Pathauto 6.x-1.x-dev (2008-Mar-07)
Token 6.x-1.10
Views 6.x-2.0-alpha3
Comments
Comment #1
merlinofchaos commentedCan you try disabling all non-core modules and trying this? I've never run into a problem with Views using tons of memory, and I'm wondering if there's some interaction with one of those modules you list that I'm not seeing.
(You can leave Devel and DHTML Menu on; I use those, so those are likely not interfering. But it's worth checking Image, Pathauto and Token).
Comment #2
karens commentedYou should also update to the latest development version of Views and see if you still have a problem there.
Comment #3
merlinofchaos commentedSetting to needs more info while awaiting feedback.
Comment #4
ibot commentedthanks for your answers!
But i'm sorry, currently i can not reproduce this error anymore :-/
Installed modules are the same...
Comment #5
ibot commentedUuups, sorry
- i was looking in the wrong drupal-installation...
Now i disabled these modules:
- image
- pathauto
- token
but no change...
Comment #6
ibot commentedAlso updating to views-6.x-2.0-alpha4.tar.gz was no solution.
Comment #7
ansorg commentedhm, 512MB not enough? Wow :(
I just set up a new drupal-6.1 to try new things. Server limit is 15MB, Views is alpha4
on the empty homepage I get
on the module page: 8.5MB => 10.5MB => 11MB
But I have another drupal 6.1 page where, after uploading "views" and enabling the module, the module list first complained about exceeded memory limit and from there on would show only a blank page. I had to delete the module folder from filesystem to get my module list back :(
On a drupal-5.7 site with CCK and Views and lots of other stuff I never exceeded the 15MB limit.
Jens
Comment #8
drewish commented15 MB isn't much, most stock php.ini files i've seen start at 32M...
Comment #9
www.richardsprojects.co.uk commentedI had this problem when the Developer module was enabled. It was caused by an endless loop somewhere and it didn't matter what I increased the memory too. I've not had this problem when the Developer module wasn't enabled.
Comment #10
merlinofchaos commentedDoes this still happen?
Comment #11
ansorg commentedUsing Drupal-6.2, views-6.x-2.0-beta1, cck-6.x-1.0-alpha (and a bunch of others)
Without Views and Views-UI: about 13 MB
with booth enabled: about 17 MB
Compared to drupal-5.x versions where views+UI increases memory usage by about 1.5 MB it seems a lot. Is there so much new functionality?
Fortunately I could increase the memory limit so it's not an issue for me right now.
Comment #12
merlinofchaos commentedI dunno. I'm testing with Views 2 and CCK and my memory limit is set at 16m; I never get close to it. Though I am using an opcode cache, which reduces the memory limit. Code still takes up memory.
Comment #13
dman commentedClean-up Views issue queue as per #572248: Mark "won't fix" any open issue that does not conform to the submission guidelines
This appears resolved - as much as it can be