The error you saw doesn't surprise me...here's the deal, I'll try to keep the nerd-speak to a minimum.
Google maps uses something called overlays for the push-pins - a unique script needs to run for every push-pin on the map. The scripts runs on the client, not on the server - so, the faster your computer, and the more memory you have, the faster the map will load.
Firefox is telling you the truth - loading the map takes a lot of resources. If you are low on available memory or your CPU is heavily loaded, loading the map can take a looooong time, and Firefox gives you the option of bailing.
It became clear rather quickly that having many push-pins slows the loading of the map considerably - once it loads, everything is fine. To demonstrate this, if you click one of the push-pins in the legend with relatively few boats (i.e. anything other than 22 or 25), the map loads very fast.
The "sweet spot" with our current code seems to be around 50 push-pins or less - this loads the map very fast, even on relatively slow computers. There are two ways to address this:
- Limit the push-pins on the initial map
- Optimize the code that loads the map
I'm looking into both, but you can only optimize code so much. From what I've seen, even the most optimized Google map sites limit overlays to 200 - a small fraction of our membership. More likely than not, the permanent solution will be to have some sort of front-end to the map that limits the push-pins. This could be a form that allows you to query just the attributes you are interested in (boat model, state, user, etc.), or something like a labled push-pin per state, indicating the number of boats it has. You could then click the push-pin to zoom in and display more boats.
Short term, I'm looking into having a "Please wait while map loads..." message popup initially, just so folks know something is going on.
So for now...just be patient while the map loads. I'll get the kinks worked out.