Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

implement dispatch.retireExports for Remotables #3297

Merged
merged 2 commits into from
Jun 14, 2021
Merged

implement dispatch.retireExports for Remotables #3297

merged 2 commits into from
Jun 14, 2021

Commits on Jun 14, 2021

  1. fix(swingset): implement dispatch.retireExports for Remotables 

    This updates liveslots to implement kernel-delivered
`dispatch.retireExports`, but only when the object being retired is a
Remotable (virtual objects are left alone for now).

Retiring an exported Remotable means we remove it from the `slotToVal` and
`valToSlot` tables, and unregister it from the `droppedRegistry`. At this
point, vat code might still hold a strong reference to the Remoteable, but
liveslots is unaware of it. If the vat re-exports the object, it will get a
new vref.
    @warner
    warner committed Jun 14, 2021
    Configuration menu
    Copy the full SHA
    e8b0f3a View commit details
    Browse the repository at this point in the history

  2. chore(swingset): comment out liveslots GC debug messages 

    and make some enhancements should they ever need to be restored
    @warner
    warner committed Jun 14, 2021
    Configuration menu
    Copy the full SHA
    3aae476 View commit details
    Browse the repository at this point in the history