# Unhandled exception: OutOfMemoryError: Isolate allocation failed due to memory limit

- **ID:** `flutter/isolate-memory-limit`
- **Domain:** flutter
- **Category:** resource_error
- **Error Code:** `OutOfMemoryError`
- **Verification:** ai_generated
- **Fix Rate:** 80%

## Root Cause

A Dart isolate exceeded its memory budget (default ~100MB on mobile), often caused by loading large datasets or infinite recursion within the isolate without proper disposal.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| Flutter 3.10 | active | — | — |
| Dart 3.0 | active | — | — |
| Android 12 | active | — | — |
| iOS 15 | active | — | — |

## Workarounds

1. **Process data in chunks: split the large dataset into smaller batches and send each batch to the isolate using `SendPort.send`. Example: `for (var i = 0; i < data.length; i += chunkSize) { isolateSendPort.send(data.sublist(i, min(i+chunkSize, data.length))); }`** (85% success)
   ```
   Process data in chunks: split the large dataset into smaller batches and send each batch to the isolate using `SendPort.send`. Example: `for (var i = 0; i < data.length; i += chunkSize) { isolateSendPort.send(data.sublist(i, min(i+chunkSize, data.length))); }`
   ```
2. **Use streaming isolates with `Isolate.stream` or `ReceivePort` to handle data incrementally, releasing memory after each chunk is processed.** (80% success)
   ```
   Use streaming isolates with `Isolate.stream` or `ReceivePort` to handle data incrementally, releasing memory after each chunk is processed.
   ```
3. **Optimize data structures: replace large lists with iterators or lazy generators that don't load all data into memory at once.** (75% success)
   ```
   Optimize data structures: replace large lists with iterators or lazy generators that don't load all data into memory at once.
   ```

## Dead Ends

- **** — The `maxMemory` parameter is not supported on mobile platforms; the limit is enforced by the operating system and cannot be increased by the app. (90% fail)
- **** — `Compute` still runs in an isolate with the same memory constraints; passing a large list directly will still cause OOM. (70% fail)
- **** — Assertions do not prevent OOM; they only check logical conditions. Memory allocation failures are not caught by assertions. (85% fail)