This one is similar to http://drupal.org/node/1114316, which was left unanswered..

With PHP memory set to 96M (hosting limit), and a Drupal 7.8 simple site (Views, WYSIWYG, Date, OL modules), I get the memory allocation error (hit the 96M limit):
"Fatal error: Allowed memory size of 100663296 bytes exhausted (tried to allocate 45 bytes) in /home/soligan3/public_html/solitest/sites/all/modules/views/includes/base.inc on line 119".

Is this just a fact of life, or is there a way to control memory usage by OL (I am quite sure it's an OL issue)?
I am using Chrome 13.0 on Win 7, if it matters.

Comments

zzolo’s picture

zzolo CreditAttribution: zzolo commented

Hi @rond49. This is a very difficult issue to debug. Your errors do not indicate OpenLayers at all (but of course this could be the culprit).

Do you have a lot modules installed? Can you install a simple Drupal site and enable only the relevant modules?

rond49’s picture

rond49 CreditAttribution: rond49 commented

I know it's tricky and difficult.
I use Chaos tools, Date, Node reference, Pathauto, Wysiwyg and Views.
Moreover, it works fine locally, but when hosted on Siteground, it freezes for a minute when I edit a map (probably a slow query) and then spits out the memory error message.
I will try to start from scratch...

rond49’s picture

rond49 CreditAttribution: rond49 commented
Status: Active » Closed (cannot reproduce)

Tries to reproduce the error, but couldn't.
Will reopen if I can reproduce it starting from a fresh site.
Sorry.

jeremymcminn’s picture

jeremymcminn CreditAttribution: jeremymcminn commented

I am having the same issues, memory problems when I try to setup a view with an OL Map.

carsonw’s picture

carsonw
handsome / brilliant
CreditAttribution: carsonw commented

Same issues here... "Allowed memory size of 268435456 bytes exhausted" when trying to view map page after following detailed instructions in the handbook.

carsonw’s picture

carsonw
handsome / brilliant
CreditAttribution: carsonw commented

This is how I solved my problem:

#1: Created a view with the display type of "OpenLayers Data Display," added the appropriate filters & fields, and configured the format settings to utilize the correct longitude and latitude fields
#2: Went to edit my OpenLayersMap at admin/structure/openlayers/maps/... and enabled the above view as an overlay layer.
#3: Created a separate, altogether new view with a display type of "Page" and altered the format to "OpenLayers Map" and chose my OpenLayers Map

The problem was that I was trying to do Step 1 and 3 in one united view with multiple displays. By separating it out into two views, I stopped getting the memory error anytime I wanted to view my map.

jamix’s picture

jamix CreditAttribution: jamix commented

In my case, I simply forgot to set the "For:" checkbox to "This page (override)" when creating the OpenLayers Map display page in the view. That caused my OpenLayers Data Overlay display to also get the "OpenLayers Map" format. Fixing this made the PHP memory error disappear.

nally’s picture

nally CreditAttribution: nally commented

Thanks @jamix

I'd fallen into the same trap (kind of obvious in retrospect!), so I changed the docs I was following in hopes of preventing the same (simple) pitfall for others.