Benjamin Smedberg bad093c6b3 Bug 561817 part A: Entered/ExitedCall callbacks for toplevel actors upon RPC in-calls. r=bsmedberg		2010-04-29 11:49:00 -05:00
..
AsyncChannel.cpp	Bug 545733: |const|-ify some *Channel methods. r=bent	2010-04-27 00:42:59 -05:00
AsyncChannel.h	Bug 545733: |const|-ify some *Channel methods. r=bent	2010-04-27 00:42:59 -05:00
BrowserProcessSubThread.cpp	Bug 516515 - Don't initialize XPCOM in plugin processes, r=cjones	2010-02-03 17:17:09 -05:00
BrowserProcessSubThread.h	Bug 516515 - Don't initialize XPCOM in plugin processes, r=cjones	2010-02-03 17:17:09 -05:00
GeckoChildProcessHost.cpp	Bug 553904 - Child tab process crashes on attempt to initialize child plugin process. r=bent.mozilla	2010-04-20 21:43:51 +03:00
GeckoChildProcessHost.h	Bug 542053: Set LD_LIBRARY_PATH=[GRE dir] for mozilla-runtime on linux. r=bsmedberg	2010-04-09 15:03:08 -05:00
IPCMessageUtils.h	Bug 547881 - Made a mistake when fixing a nit. r=me	2010-03-24 09:20:36 -07:00
Makefile.in	Bug 548437: Add a SysV shmem subtype of SharedMemory. r=dougt	2010-04-16 00:29:16 -05:00
MessagePump.cpp	Fix PostDelayedTask in the message loop	2009-11-23 16:01:12 -05:00
MessagePump.h	Fix PostDelayedTask in the message loop	2009-11-23 16:01:12 -05:00
MozillaChildThread.cpp	Bug 553904 - Child tab process crashes on attempt to initialize child plugin process. r=bent.mozilla	2010-04-20 21:43:51 +03:00
MozillaChildThread.h	Bug 516515 - Don't initialize XPCOM in plugin processes, r=cjones	2010-02-03 17:17:09 -05:00
ProtocolUtils.h	Bug 555275: Implement a DeallocShmem() interface. r=bent	2010-04-26 20:11:40 -05:00
RPCChannel.cpp	Bug 561871 part B: don't use Windows events to enter/exit a nested event loop within an RPC stack frame, because delivery of those events isn't always associated with the correct stack frame, and also because the events can be lost if they race with an incoming RPC reply message. Instead, keep a linked list (on the stack) of RPC frames globally and per-channel, to associate requests to enter a nested event loop with the correct frame, r=jimm	2010-04-28 11:01:09 -04:00
RPCChannel.h	Bug 561817 part A: Entered/ExitedCall callbacks for toplevel actors upon RPC in-calls. r=bsmedberg	2010-04-29 11:49:00 -05:00
ScopedXREEmbed.cpp	Bug 523417 - "warning: invoking macro NS_ENSURE_SUCCESS argument 2: empty macro arguments are undefined in ISO C90 and ISO C++98" in DOM worker code. r=jst	2010-02-22 18:41:21 +01:00
ScopedXREEmbed.h	…
SharedMemory.h	Bug 548437: Add a SysV shmem subtype of SharedMemory. r=dougt	2010-04-16 00:29:16 -05:00
SharedMemoryBasic.h	Bug 548437: Add a SysV shmem subtype of SharedMemory. r=dougt	2010-04-16 00:29:16 -05:00
SharedMemorySysV.h	Bug 548437: Add a SysV shmem subtype of SharedMemory. r=dougt	2010-04-16 00:29:16 -05:00
SharedMemory_posix.cpp	bug 523174: add a higher-level Shmem class that implements exclusive access rights between parent/child actors and does over/underflow checking. (Also adds a stop-gap lower-level SharedMemory class in lieu of bug 523172.) r=joedrew	2009-12-04 12:45:15 -06:00
SharedMemory_windows.cpp	bug 523174: add a higher-level Shmem class that implements exclusive access rights between parent/child actors and does over/underflow checking. (Also adds a stop-gap lower-level SharedMemory class in lieu of bug 523172.) r=joedrew	2009-12-04 12:45:15 -06:00
Shmem.cpp	Bug 555275: Implement a DeallocShmem() interface. r=bent	2010-04-26 20:11:40 -05:00
Shmem.h	Bug 555275: Implement a DeallocShmem() interface. r=bent	2010-04-26 20:11:40 -05:00
StringUtil.cpp	…
SyncChannel.cpp	Bug 561871 part B: don't use Windows events to enter/exit a nested event loop within an RPC stack frame, because delivery of those events isn't always associated with the correct stack frame, and also because the events can be lost if they race with an incoming RPC reply message. Instead, keep a linked list (on the stack) of RPC frames globally and per-channel, to associate requests to enter a nested event loop with the correct frame, r=jimm	2010-04-28 11:01:09 -04:00
SyncChannel.h	Bug 561871 part B: don't use Windows events to enter/exit a nested event loop within an RPC stack frame, because delivery of those events isn't always associated with the correct stack frame, and also because the events can be lost if they race with an incoming RPC reply message. Instead, keep a linked list (on the stack) of RPC frames globally and per-channel, to associate requests to enter a nested event loop with the correct frame, r=jimm	2010-04-28 11:01:09 -04:00
WindowsMessageLoop.cpp	Bug 561871 part B: don't use Windows events to enter/exit a nested event loop within an RPC stack frame, because delivery of those events isn't always associated with the correct stack frame, and also because the events can be lost if they race with an incoming RPC reply message. Instead, keep a linked list (on the stack) of RPC frames globally and per-channel, to associate requests to enter a nested event loop with the correct frame, r=jimm	2010-04-28 11:01:09 -04:00
WindowsMessageLoop.h	Bug 545760 - '[OOPP] Fix a few bad DefWindowProc messages that slipped through'. WM_SETICON. r=jimm.	2010-02-18 12:11:31 -08:00