cursorWindowSize

Maximum number of rows in each cursor-window segment, Int.MAX_VALUE to use one segment.

Scrollable queries are stepped once and materialised into one or more segments. Segmenting avoids very large individual native allocations, but total cursor memory remains proportional to the result-set size. It also gives the cursor a stable snapshot: later movement does not re-run the query.

Callers processing large results sequentially should use a forward-only API, which retains only the current SQLite row instead of materialising the result.

Scrollable cursors are not thread safe and must not be accessed concurrently from multiple threads. Cross-thread hand-off requires the caller to provide the usual happens-before relationship.