I implemented a simple workaround like this:

void WasteBin::PostUpdate(const UpdateInfo & _info, const EntityComponentManager & _ecm)
{
  if (_info.paused) return;
  if (!this->dataPtr->configured) return;

  if (!this->dataPtr->model.Valid(_ecm))
  {
    gzwarn << "Model <" << this->dataPtr->modelName << "> no longer valid. "
           << "Disabling WasteBin plugin." << std::endl;
    this->dataPtr->configured = false;
    return;
  }

  [...]

}

While this works well, it has following drawbacks:

• It is yet some additional code to implement in each model or sensor plugin; prone to be forgotten etc.
• I assume the call to model.Valid(_ecm) has a non-negligable computational cost, which would be avoided if a proper solution was implemented.

So I still feel that model and sensor plugins should be disabled (or removed) automatically upon removal of the corresponding model or sensor.

Another example:

• Add a model with some joints having a JointPositionController plugin,
• Remove that model

Result:

Flood of error messages:

[Err] [EntityComponentManager.cc:1083] Trying to create a component of type [8319580315957903596] attached to entity [47], but this entity does not exist. This create component request will be ignored.

I 'fixed' this in my local tree with a similar workaround as above, but meh...

void JointPositionController::PreUpdate(
    const UpdateInfo &_info,
    EntityComponentManager &_ecm)
{
  GZ_PROFILE("JointPositionController::PreUpdate");

  if (kNullEntity == this->dataPtr->model.Entity())
  {
    return;
  }

  if (!this->dataPtr->model.Valid(_ecm))
  {
    gzwarn << "JointPositionController model no longer valid. "
           << "Disabling plugin." << std::endl;
    this->dataPtr->model = Model(kNullEntity);
    return;
  }

  [...]

}

Yes currently the SystemManager does not support removal of plugins. This seems to be something that can be fixed, but will take some amount of effort.

Latching on to this: I get an entity does not exist error after removing a model that was spawned using the resource spawner. I think this is probably related to this issue. (Using gazebo garden)

Yeah. That is expected I'm currently working on a fix for it here: #2232