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
..
lib	Don't send ATOM_BROWSER_DEREFERENCE message if context is already gone.	2013-05-04 23:00:57 +08:00
atom_api_renderer_ipc.cc	Add ipc.sendSync in renderer.	2013-04-23 21:52:19 +08:00
atom_api_renderer_ipc.h	Add ipc.sendSync in renderer.	2013-04-23 21:52:19 +08:00
atom_renderer_bindings.cc	small tune of IPC interface.	2013-04-23 20:57:14 +08:00
atom_renderer_bindings.h	small tune of IPC interface.	2013-04-23 20:57:14 +08:00