Allocation size overflow about location-history-visualizer HOT 9 CLOSED

Hey, thanks for message! Sorry you're encountering that error. It sounds like some sort of memory limitation in JavaScript -- I've processed a file ~300mb with no problems, though, so maybe it's on an individual basis? I'd need to do some more experimentation.

Although it's not really a solution, in ba28320 I did add an alternate upload method that uses Google's internal KML endpoint as opposed to Google Takeout – the KML file is much smaller than the JSON from Takeout, so maybe it's worth giving that a shot... (just use the link on the homepage of the visualizer).

Hope this helps! Please let me know what you discover.

from location-history-visualizer.

Hmm, that doesn't work either it seems. Ending up with (error: Unexpected token <)

from location-history-visualizer.

Your browser may be using a cached version of the JavaScript... Try shift-reloading, perhaps? (The file index.js should match that in the master branch.)

from location-history-visualizer.

I get that last error when dragging the downloaded KML onto the site. Even after I tried to shift-reload the tool.

from location-history-visualizer.

Sounds like maybe GitHub Pages is doing some caching on its own... I just tried to initiate a cache purge. Maybe that will help.

Sorry for the difficulty getting this working! Can you verify that the index.js file you're being served contains the string "kml"?

from location-history-visualizer.

The reason I feel like you're getting a cached file is because the Unexpected token error is a JSON.parse error, not from the KML parser... Which means either you're getting an old version of the js or there's something wrong in the KML detection.

from location-history-visualizer.

Yep, index.js contains a method called getLocationDataFromKml().

from location-history-visualizer.

Really strange. You tried uploading again after you verified that the getLocationDataFromKml method was present, and you still saw that error? Hmm...

from location-history-visualizer.

I did.

from location-history-visualizer.