"win" Object passed to "i18next-electron-fs-backend" has been destroyed

Even I change the “close” event handler to:

  win.on('closed', event => {
    event.preventDefault();
  });

The win object still got destroyed, because I can change “activate” handler to this:

app.on('activate', () => {
  if (win.isDestroyed()) {
    createWindow();
  }
});

And it will recreate the window. This means, though win is not null, it is actually destroyed.

And this resulted in the following error:

Uncaught Exception:
Error: Object has been destroyed
    at BrowserWindow.<anonymous> (/xxx/node_modules/i18next-electron-fs-backend/lib/index.js:1:2472)
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:61:3)

[reZach]

@linonetwo I’ve commented the fix here. The issue has been fixed in the i18next-electron-fs-backend package. You should get version 1.1.2 for the fix and add the code mentioned in the comment.

[linonetwo]

No, I still get Object has been destroyed:

I think we can’t prevent win object to be destroyed, we can only try no to use it if it is destroyed.

I’m doing so in IPC related code:

ipcMain.on('start-server', async (event, args) => {
  // prevent "Object has been destroyed" error, after await, win may have destroyed due to close of window
  const reply = (...params) => event.sender.isDestroyed() ? null : event.reply(...params)

// ...
          reply('generate-keys-succeed');
// ...

Maybe you have to check win.isDestroyed() in i18next-electron-fs-backend? So this might still belongs to i18next-electron-fs-backend side.

I guess this only happened in MacOS, where the main process is still running, so i18next-electron-fs-backend still trying to send something to the window, but windows are actually all destroyed.