Issue Details

• Electron Version:
  • 3.x, 4.x, 5.x, 6.x
• Operating System:
  • All
• Last Known Working Electron version::
  • 2.x

Expected Behavior

When navigations occur, a new process should be created for the navigation.

Actual Behavior

When a navigation occurs during a preloads scripts execution the same process is re-used as Chromium does not think the navigation has been committed yet. This causes a memory leak and all native node modules to break.

To Reproduce

Fiddle: https://gist.github.com/MarshallOfSound/c89aa0037c3da114d44aa3a2d1a0fc24

Screenshots

As you can see here there are three navigation loads, the second and the third one actually have the same process ID (and are running in the same process)