This was set as a topcrash, because one of the win32k lockdown enablements caused a spike.
Bug 1719212 Comment 17 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This was set as a topcrash, because win32k lockdown caused a spike in earlier windows.