electron/spec/fixtures/crash-cases/webcontents-create-leak-exit/index.js

const { app, webContents } = require('electron');
app.whenReady().then(function () {
  webContents.create();

  app.quit();
});
fix: destroy WebContents synchronously on shutdown (#15541) 2018-11-08 15:57:28 +00:00			`const { app, webContents } = require('electron');`
refactor: prefer using app.whenReady() (#21972) * docs: add references to app.whenReady() in isReady * refactor: prefer app.whenReady() In the docs, specs, and lib, replace instances of `app.once('ready')` (seen occasionally) and `app.on('ready')` (extremely common) with `app.whenReady()`. It's better to encourage users to use whenReady(): 1. it handles the edge case of registering for 'ready' after it's fired 2. it avoids the minor wart of leaving an active listener alive for an event that wll never fire again 2020-02-03 22:43:22 +00:00			`app.whenReady().then(function () {`
test: use webContents.create() in type-safe way (#37281) test: use (webContents as typeof ElectronInternal.WebContents).create() Co-authored-by: Milan Burda <miburda@microsoft.com> 2023-02-16 14:41:41 +00:00			`webContents.create();`
fix: destroy WebContents synchronously on shutdown (#15541) 2018-11-08 15:57:28 +00:00
fix: quit after Chromium is fully started (#21488) * fix: quit when chromium is fully started * test: remove hacks on app.quit * chore: RunUntilIdle is unnecessary 2019-12-13 09:57:02 +00:00			`app.quit();`
fix: destroy WebContents synchronously on shutdown (#15541) 2018-11-08 15:57:28 +00:00			`});`