@hiphauler You repeatedly tried to deactivate and it timed out each time? Do other plugins timeout when deactivating?
today there was the same problem as the previous assessment
@fox056 Does it happen with only deactivating the AMP plugin or deactivating any plugin?
Note that the AMP plugin does do a loopback request to the frontend of the site after a plugin is activated to check for incompatibilities: https://github.com/ampproject/amp-wp/blob/d8b0cac757c2cfeae384e522aea00ece0dee5a25/includes/validation/class-amp-validation-manager.php#L175-L182
However, this should not happen at deactivation as seen in this code.
It would be ideal if you could open a support topic to help us find a solution to the problem.
Happened with me too but for some other plugin. It’s not just this plugin but could be any plugin. Disable object caching before deactivating any plugin as you keep seeing the old page from cache. That should resolve this issue.
