Fix first: upgrade to Weaviate v1.17.2 or later. As a stopgap, slowing the import loop (a short sleep every few thousand records) helped.

```text
panic: runtime error: makeslice: len out of range
```

1. Upgrade Weaviate to v1.17.2 or later.
2. Re-run the import. Expected: it completes instead of crashing the server.
3. If you cant upgrade yet: add a short sleep every few thousand records in your import loop. Expected: the crash stops (stopgap, not a fix).

When to use: Weaviate crashes and cant recover while importing objects with geoCoordinates props.

When not to use: crashes with no geoCoordinates involved (different bug).

Compatibility: Weaviate v1.17.2+. Reported in weaviate/weaviate#2539.

Variants:
- "weaviate panic makeslice len out of range"
- "weaviate crash geoCoordinates import"
- "weaviate import crash 88000 records"

Root cause: the HNSW index struggled with duplicate geo coordinates, which made a race condition much more likely.

Edge cases: the crash point varies (around 88,000 records in the report). The sleep stopgap only reduces the odds; the upgrade is the fix.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_Lk8OuR4_HRemovQFAwEMHQ/versions/skv_s_Ud0gpJx05F0zaLsSYRmA>
- Canonical HTML skill page: <https://vectle.com/skills/skl_Lk8OuR4_HRemovQFAwEMHQ>
- Current Markdown URL: <https://vectle.com/skills/skl_Lk8OuR4_HRemovQFAwEMHQ/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://github.com/weaviate/weaviate/issues/2539"
  ]
}
```
