Removing custom allocator in the desktop app

[deepak1556]

In the upcoming release v1.94 of VSCode, we have removed the custom alloctor that was added in v1.78 to the desktop application extension host to act as a bridge to support V8 sandbox incompatible Node.js native addons built against the Electron runtime. You can refer to this tracking issue for additional context. We have ensured that the top 5000 extensions are unaffected by this change. If your extension or a dependency of your extension is affected, here are some suggestions:

1. If your extension uses n-api then the status napi_no_external_buffers_allowed will be returned when using external array buffers. In which case, you can switch to use the copy version of the API napi_create_buffer_copy.
2. If your extension uses node-addon-api then refer to this document for alternative API and compile time settings.
3. If you want to avoid the performance cost from the copy, you can use the allocator from V8 to ensure the buffer backing store is compatible with the V8 sandbox.

We have also added telemetry points to identify extensions and native addons that could be affected, so we can proactively reach out to extension authors and offer help were possible. If your extension is effected, and none of the above suggestions work for you please comment here and we will gladly help.