Have been playing with node-webkit for few months, it has its pros, but quirks as well. Such as...... memory leak.

As a web developer who cannot fix any problem of the browser, a common workaround would be reloading the page, and hoping the browser will release everything, except it won't.

So here is another workaround for node-webkit:

var win = require('nw.gui').Window.get();
win.reload(3);
//or
win.reloadDev();

as mentioned in #149.

These are not documented, but are used internally when the reload button of the toolbar is pressed. After digging through the code, seems that this part is called when reload(3) is called, but not other type of reload.

Hope this will help someone:)

Blog Logo

b123400


Published