Calling setMap(null) on an object too soon after it is created is raising an error within the API. The error is a little different between browsers but occurs in all that I have tested. It is usually something like "a is undefined" (firefox), "Uncaught TypeError: Cannot call method 'setPaths' of undefined" (Chrome), or "SCRIPT5007: Unable to get value of the property 'setPaths': object is null or undefined" (IE9). I presume this is occurring because the maps api has readied itself to render the overlay but hasn't gotten around to doing it until after setMap(null) has already been called.

A test fixture is attached that illustrates this problem in API version 3.4; however the issue currently exists in all versions of the 3.x API.

test34.html 1.4 KB   View   Download