06a00b74e8
* fix: initialize asar support in worker threads Use `ObjectWrap` instead of gin's Wrap in `electron_api_asar.cc` because gin isn't fully initialized (and apparently not possible to initialize without ruining the isolate configuration and array buffer allocator) in worker threads. In the worker thread call `setupAsarSupport` just as we do for the main process. * Update lib/asar/fs-wrapper.ts Co-authored-by: Darshan Sen <raisinten@gmail.com> * Update patches/node/worker_thread_add_asar_support.patch Co-authored-by: Darshan Sen <raisinten@gmail.com> * Add a test Co-authored-by: Darshan Sen <raisinten@gmail.com> Co-authored-by: Fedor Indutny <79877362+indutny-signal@users.noreply.github.com> Co-authored-by: John Kleinschmidt <jkleinsc@electronjs.org> |
||
---|---|---|
.. | ||
configs | ||
fixtures | ||
static | ||
ts-smoke | ||
.eslintrc | ||
api-clipboard-spec.js | ||
api-native-image-spec.js | ||
api-process-spec.js | ||
api-shell-spec.js | ||
api-web-frame-spec.js | ||
asar-spec.js | ||
BUILD.gn | ||
chromium-spec.js | ||
events-helpers.js | ||
expect-helpers.js | ||
global-paths.js | ||
node-spec.js | ||
package.json | ||
spec-helpers.js | ||
webview-spec.js | ||
yarn.lock |