Row ceilings applied to the data bridges the component under test calls through
(__mjRunView, __mjRunViews, __mjRunQuery).
A test run only needs enough rows to render and be looked at, so the harness does not
honour an unbounded request. MaxRows is applied at the SQL level by the provider, so
the surplus is never produced rather than fetched and discarded — which matters because
a bridge result is serialized in Node, shipped over CDP and rehydrated in Chromium,
leaving several resident copies of the same data.
Row ceilings applied to the data bridges the component under test calls through (
__mjRunView,__mjRunViews,__mjRunQuery).A test run only needs enough rows to render and be looked at, so the harness does not honour an unbounded request.
MaxRowsis applied at the SQL level by the provider, so the surplus is never produced rather than fetched and discarded — which matters because a bridge result is serialized in Node, shipped over CDP and rehydrated in Chromium, leaving several resident copies of the same data.