devot:eeDevoted to ExpressionEngine

Hey -

I’ve a channel with ~550 locations brought in through the importer and geolocated (with about 20% errors due to bad data).

Trying to search against them I get:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 85 bytes) in /www/eh6321/public_html/ee2/system/expressionengine/third_party/gmap/mod.gmap.php on line 2141

EE current has 64M of memory available.

Looking through past support threads I see reference to a “new add-on” - is that your Geocoder? If so, how will that being added into the install affect the import process, and/or the templating?

Whups - I meant to post this in the Googlemaps for ExpressionEngine forum.

The new add-on I was referring to is Channel Search, which isn’t on Devotee yet.

https://objectivehtml.com/channel-search

After looking at the line of code causing this error, my guess is you have a rather large dataset and looping through it all to prepare to parse in the template is causing the high memory usage. My immediate recommendation would be to paginate your results. Channel Search on the other hand has better performance, easier pagination, and uses GET queries to perform the search.

Also, regarding the errors in the import, I am working on an update that will help with this. I don’t have this update made yet, so I can get you that once I have it available, but it could cut down your errors by 50%. I am not sure this will take care of all the error in the import, but it could help with some of them. it really just depends on how “bad” your data is. I do know for certain though, the failed geocodings won’t cause memory limit issues. How many records are you searching?

I did have 550-ish records, but that is only part of the dataset which will have roughly 2K total when they are all in.

I removed the text-listings under the map and it loads without error now - but I need to do some tweaking yet I think.

Hard to say the severity of the data errors. I’ve played with a few of the failed imported records and seems that when I copy and paste the address that failed into the fieldtype it finds it successfully.

Yup, that’s the bug I am working on. I think Google changed something with their import script so that if it goes over the limit, the last record attempting to be geocoded always fails. It use to not do this, and I have tested Google Maps for EE with a record set of 80,000 entries, so I know it works for large datasets.