Selecting a physical vehicle that another resident is driving — by entering edit mode (Ctrl-3) and clicking it, or by right-clicking it so the context menu opens — stops the vehicle dead for as long as the selection is held. The selecting avatar needs no permissions on the object: not owner, not group, no modify rights. On deselect the vehicle resumes from zero velocity.

This is being used (accidentally and otherwise) to disrupt organized racing: a spectator right-clicking a passing car to inspect it halts that car mid-lap.

The same behavior was reported as SVC-34 ("Right-clicking another Resident's moving object freezes it") and listed as fixed in server release 11.09.23.241511, alongside "Anybody can freeze an unscripted physical object." The edit-mode selection path still reproduces in 2026. Linden Lab's own QA test script acknowledges it — Object Selection Test, "Select other's vehicles": "verify you can select other's vehicles and their vehicle stops. Unfortunate." (page last edited October 2013).

No script-side mitigation exists: STATUS_BLOCK_GRAB does not affect selection (and the same test page notes it doesn't work anyway), the Locked checkbox only restricts the owner, and disabling Build on the parcel does not block selection.

## Steps to reproduce

## Expected behavior

Selecting an object you cannot modify should not alter its simulation. Physics should only be suspended for a selection by an agent who has modify rights on the object (owner, or group with appropriate permissions), and ideally only when that agent begins an edit operation.

## Actual behavior

Physics is suspended for any selection, regardless of the selecting agent's permissions on the object.

## Environment

## References