Cheng Zhao d377cbfa74 Don't send ATOM_BROWSER_DEREFERENCE message if context is already gone. ... It's possible that the object gets destructed after reloading, however since we already released all objects in browser when unloading, it would cause troubles when sending message in an unexist context. We just rely on the closure to mark whether the context is gone. A more suitable solution, however, is to restart renderer process when doing reloading.		2013-05-04 23:00:57 +08:00
..
dialog.coffee	Add dialog API.	2013-05-03 19:31:24 +08:00
ipc.coffee	Clear listeners on process object when unloading.	2013-05-04 21:52:14 +08:00
remote.coffee	Don't send ATOM_BROWSER_DEREFERENCE message if context is already gone.	2013-05-04 23:00:57 +08:00