What a weird take. If this bug was engineered as an attack on Firefox, then it seems like the project has been infiltrated by bad actors, because the bug comes from Firefox's codebase. Indeed, the developers themselves contradict your comment in the linked bug conversation:
> This problem has two sides: Microsoft was doing a lot of useless computations upon each event; and we are generating a lot of events. The combination is explosive. Now that Microsoft has done their part of the job (comment 82), we need to reduce our dependency to VirtualProtect.
Compare how many calls other browsers make (this is also quoted in the link): Firefox was generating up to 46 times more (costly) events than Chrome. It is a bit ludicrous to shame Microsoft for the whole situation.
> Firefox with normal configuration: ~14000 events, 98% of which are PROTECTVM_LOCAL;
> Firefox with the preferences from comment 83: ~6500 events, 95% of which are PROTECTVM_LOCAL;
> Edge: ~2000 events, 91% of which are ALLOCVM_LOCAL;
> This problem has two sides: Microsoft was doing a lot of useless computations upon each event; and we are generating a lot of events. The combination is explosive. Now that Microsoft has done their part of the job (comment 82), we need to reduce our dependency to VirtualProtect.
(https://bugzilla.mozilla.org/show_bug.cgi?id=1441918#c90)
Compare how many calls other browsers make (this is also quoted in the link): Firefox was generating up to 46 times more (costly) events than Chrome. It is a bit ludicrous to shame Microsoft for the whole situation.
> Firefox with normal configuration: ~14000 events, 98% of which are PROTECTVM_LOCAL;
> Firefox with the preferences from comment 83: ~6500 events, 95% of which are PROTECTVM_LOCAL;
> Edge: ~2000 events, 91% of which are ALLOCVM_LOCAL;
> Chrome: ~300 events.