Issue 331 - earth-api-samples - fetchKml() fails on slower connections or fast connections and large KML/KMZ files

Issue 331:	fetchKml() fails on slower connections or fast connections and large KML/KMZ files
	12 people starred this issue and may be notified of changes.	Back to list

Status:	Fixed
Owner:	----
Closed:	Sep 22
Type-Defect
Priority-Medium
Component-Plugin
Internal-2115082

Reported by michael.sebastian.castro, Sep 14, 2009

What steps will reproduce the problem?
1.Attempt fetchKml() from slow server - 
http://dev.sybilmedia.com/GEP/regions_combined.kmz
2.Attempt fetchKml() from fast server - 
http://orangecms.com/regions_combined.kmz
3.Observe that the same kmz file fails from the slow server and succeeds 
when pulled from the fast server. (Minimum 5Mbps downstream client 
connection required to observe the effects)

What is the expected output or behavior? What do you see instead?

Expected output is a successful kmlObject for the fetchKml() callback 
function regardless of the client connection speed or server speed.

Actual output varies on client connection speed or server speed. Usual 
output from a slow connection (client or server) is a null or bad 
kmlObject passed to the fetchKml() callback function.

Which plugin version are you using?

Installed Plugin Version: 5.1.3506.3999

Which browsers and operating systems are affected?

Tested on FF3, IE7, 8 WinXP, Vista

Please provide any additional information (code snippets/links) below.

Observation: Using a broadband card for my PC (about 500Kbps downstream), 
any KML/KMZ file fails if it is above 700KB in size.

The above links can be tested in the Code Playground with the Fetch KML 
(interactive) example.

Comment 1 by api.roman.public, Sep 14, 2009

Thanks for the detailed bug report!

Status: Confirmed
Labels: Component-Plugin Internal-2115082

Comment 2 by mattfox, Sep 14, 2009

This appears to be related to an issue introduced in Google Earth 5.1.  To test. 
Create a network link using either of the links posted above in Google Earth.  They
will fail to load.  On my computer with 15 MB connection any KMZ file over about 1
megabyte will fail to load via network link in Google Earth or via a URL in a
Balloon.  KMZ files under 1 megabyte fetch no problem.

Comment 3 by greg.angevine, Sep 14, 2009

I think this issue occurs with KMZ files that are even smaller, such as 497KB. If the 
Earth plugin is loaded/refreshed a few times I notice the file eventually shows up. 
Once it is in the cache it opens every time, but its certainly an annoying glitch with 
the 5.1 plugin.

Comment 4 by luizrodrigotozzi, Sep 14, 2009

In my internet connection (1Mbps downstream) and my work's (20 Mbps) I can't load
KMZs/KMLs with more than 480kb since I "manually" updated the plugin (uninstalling
and installing again).

Comment 5 by api.roman.public, Sep 15, 2009

We have a fix internally; this should be fixed in our next release. I will post here
as soon as there are more details.

Status: FixedNotReleased

Comment 6 by greg.angevine, Sep 15, 2009

Thanks for the fast action. Any estimate to when that will be released? (Days or weeks?
)

Comment 7 by api.roman.public, Sep 16, 2009

No estimate yet, but as soon as possible--it's a very high priority to get this fix 
released.

Comment 8 by guilgot, Sep 19, 2009

Thanks for the fix. For information, the bug is not present in mac OS plug-in version. My application still load 
6Mo kmz file throw fetchKML() function...

As others, this new bug completly breaks my on line application for windows users ! 
Could you publish a new release this week ? Please....

Comment 9 by api.roman.public, Sep 22, 2009

Fixed as of 5.1.3509.4636, which was released today.

Status: Fixed