Spatial navigation Module Memory Documentation

$Id$

Used OOM policies

Spatial navigation uses OP_STATUS internally.

Who is handling OOM?

On OOM, spatial navigation methods return FALSE (failure).

Heap memory usage

Spatial navigation builds its own frame stack on the heap, otherwise no heap memory needed.

Stack memory usage

When moving into frames and iframes, some functions are used recursively, but that should not result in too much stack memory usage. When traversing, the layout engine uses recursion, but spatial navigation traverse should not result in more stack memory usage than other traversals (such as on paint).

Freeing memory on exit

Spatial navigation frees all its allocated memory when the window is destroyed.

Temp buffers

Temp buffers are not used.

Memory tuning

No tuning possible.

Tests

Coverage

Design choices

The main goals are the same as for Opera in general: correct, fast, low footprint and non-blocking.

Suggestions of improvements