too much recursion errors when plotting

[toofishes]

I'm not sure why, but I'm seeing this when I plot:

too much recursion http://maps.gstatic.com/intl/en_us/mapfiles/api-3/4/11/main.js Line 25 var Te=Se(-Oe,-Oe,Oe,Oe),Ue=Se(0,0,0,0...s[d])thisd;else this.set(b,c)}};

This is from Firebug in Firefox 4; Chrome's JS console doesn't show this error but I have the feeling it is blowing up on the exact same thing as the end result is the same- a map totally zoomed out and small in the upper-left corner, with absolutely nothing plotted.

Both FF and Chrome also show a bunch of these, but I have the feeling they are just debug output more than anything: plist.js:82unknown column of type 8 plist.js:82unknown column of type 8 plist.js:82unknown column of type 6 plist.js:82unknown column of type 6 plist.js:82unknown column of type 8 plist.js:82unknown column of type 8 plist.js:82unknown column of type 8 plist.js:82unknown column of type 8

(I see types 5, 6, 8, 9, 10, 11)

Other note: I could get it to work with an older backup and a consolidated.db sized at 9.6MB, this particular one is 29MB.

[toofishes]

Example of what I am seeing: http://www.toofishes.net/uploads/sqlite-iphone-map-recursion.png

[toofishes]

Not sure if this is helpful to gauge the dataset size:

sqlite> SELECT COUNT(*) FROM CellLocation;
22823
sqlite> SELECT COUNT(*) FROM CellLocationBoxes;
83119
sqlite> SELECT COUNT(*) FROM WifiLocation;
185515

[markolson]

That is indeed debug output from the sqlite reader - I had left certain types unspecified until I came across them in files I had so that I knew I'd be handeling them correctly. That may be the root cause of the other issues, but it may not. That is a somewhat higher number of CellLocation entries and who knows.

[bholland]

I see this too on my maps but my error takes the form:

Error: too much recursion Source File: http://maps.gstatic.com/intl/en_us/mapfiles/api-3/5/6a/main.js Line: 26

I only get this on certain computers but both with firefox 3.6, 4.0 and safari all on a mac. My linux box doesn't have any problems on firefox 3.6 or 4.0.