@aral Could this be a WebKit bug? Maybe Publisher is using a WebKit view and there’s a leaky sandbox or something.