Configuring nw.Window open with show:false and load timeout behavior

Goal

When opening a window with nw.Window.open(url, {show:false}, callback) the application wants to guarantee that the window is destroyed if the page does not finish loading within a configurable time interval, preventing hidden windows from staying alive and keeping associated Node.js timers, streams or child processes running.

Constraints and uncertainty

NW.js does not expose a native load‑timeout option for nw.Window.open, so developers must race a setTimeout against the loaded event and decide whether to invoke win.close(true) (force close, skipping the close event) or to let the normal close event fire so that any cancellation logic placed in a close handler runs. It is also unclear whether the close event is guaranteed to be emitted after a forced close, and how to ensure that Node.js resources tied to that window’s context are cleaned up regardless of the close path taken.

What is the recommended way to combine a load timeout with the window’s close event so that cleanup code runs exactly once, and should the timeout path use win.close(true) or rely on the default close handling?