plugin active causes post / page save to 503

Hello, Eyal;
I’m sorry to inform you that by process of elimination I drilled down to your otherwise fine plugin to cause **abnormous resource peaks when saving posts** (you can clearly see the 4 peaking-out save-attempts in https://snag.gy/NEfSOu.jpg), eventually resulting in 503 errors – which effectively renders our backend incapable of saving posts.

I’ve had the console open on the last save attempts and had my attention drawn to large numbers of lines firing and coming back in red as cancelled, pointing to gmw related operations. I’m thinking the last update is trying to do something that it somehow can’t and choking itself out by retrying over and over; but that’s just a superficial guess of mine.

The plugin is not mission critical for us atm, so offing it is noch a problem, but perhaps this is something you want to give a closer look, since it might be affecting others, too, who may rely on your product more than we do.

Cheers – LX & Team LibRa