1.2 million GPS rows crash the tab with an array buffer error

• Uncaught RangeError: Array buffer allocation failed at new Float32Array, thrown from TripsLayer.initializeState (trips-layer.js:88).
• performance.memory.usedJSHeapSize reaches 2.4 GB and does not fall after GC, so the data is retained.
• The tab title becomes 'Page unresponsive' and the canvas goes white.

1. Log record count and usedJSHeapSize before and after parsing.
2. Cut to 100k rows to confirm the crash is a scale problem rather than one bad record.
3. Check whether data is an object array from d3.csv or papaparse instead of typed arrays.
4. Inspect getPath for per-point temporary array creation.

Feed binary attributes (Float32Array positions and timestamps) through data: { length, attributes: { getPosition: { value, size: 2 } } }, load by tile or time window on moveend, and pre-build flat path arrays for TripsLayer.

Uncaught RangeError: Array buffer allocation failed
    at new Float32Array (<anonymous>)
    at TripsLayer.initializeState (trips-layer.js:88)

console.log('记录数', data.length);
console.log('堆内存 MB', (performance.memory.usedJSHeapSize / 1048576).toFixed(1));

• Keeping the original CSV object array for tooltips doubles retained memory and defeats the binary path.
• Rendering all 1.2 million rows in one TripsLayer and only lowering trailLength does not reduce the allocation.