Adding a Region to a Network link load of KML resource locks Earth and Windows

[GoogleCodeExporter]

Which products are affected?
Earth 5.0

What steps will reproduce the problem?
1. use a netbook atom/xp (you won't see this on a fast machine)
2. Load attached kmz directly; then, try again by loading with kml with
region declared.
3. without Region works as expected; with Region Earth and Windows GUIs
lock for > 1 minute 

What is the expected output or behavior? What do you see instead?
The Earth and Windows UI should not lock up during region calculation. 
Link folder progress should not freeze. Other apps should not freeze.  This
is not CPU dependent--Earth CPU sits <50% thoughout event; System idle
process remain >50% and no disk activity.

What application versions (if any) are you using?

Which operating systems and browsers are affected?

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

Original issue reported on code.google.com by paul.m...@gmail.com on 10 Mar 2009 at 9:57

Attachments:

• USCA_Airspace.kmz
• SymbolicFlightAirspaceTest_B.kml

[GoogleCodeExporter]

The kml file href is wrong...new attachment points to c:/USCA_Airspace.kmz

Same results on P4 machine with Vista and excellent graphics card.. Looks like 
the
thread assigned to core-1 is doing most of the work and ~90% load while core-0 
sits
idly by.

The point remains: Windows GUI should never lock up on an in memory process.

And why lock up AFTER the region calculation is performed?  At that point the
decision to load has been made--why does it take an order of magnitude longer 
than a
direct load of the same data?  And lock up the GUI...

Original comment by paul.m...@gmail.com on 10 Mar 2009 at 10:40

Attachments:

• SymbolicFlightAirspaceTest_B.kml

[GoogleCodeExporter]

You can test on any machine, zoom in on California and note delta in load 
times...on
atom/netbook this is dramatic.

Original comment by paul.m...@gmail.com on 10 Mar 2009 at 11:03