Name Description Size
BackgroundChild.h 2982
BackgroundChildImpl.cpp 23783
BackgroundChildImpl.h 10961
BackgroundImpl.cpp 52079
BackgroundParent.h 3739
BackgroundParentImpl.cpp 43568
BackgroundParentImpl.h 16950
BackgroundUtils.cpp 35552
BackgroundUtils.h Convert a PrincipalInfo to an nsIPrincipal. MUST be called on the main thread. 5503
BrowserProcessSubThread.cpp static 1902
BrowserProcessSubThread.h 2045
ByteBuf.h A type that can be sent without needing to make a copy during serialization. In addition the receiver can take ownership of the data to avoid having to make an additional copy. 1758
ByteBufUtils.h A type that can be sent without needing to make a copy during serialization. In addition the receiver can take ownership of the data to avoid having to make an additional copy. 1904
CrashReporterClient.cpp static 1223
CrashReporterClient.h 1383
CrashReporterHelper.h This class encapsulates the common elements of crash report handling for toplevel protocols representing processes. To use this class, you should: 1. Declare a method to initialize the crash reporter in your IPDL: `async InitCrashReporter(NativeThreadId threadId)` 2. Inherit from this class, providing the appropriate `GeckoProcessType` enum value for the template parameter PT. 3. When your protocol actor is destroyed with a reason of `AbnormalShutdown`, you should call `GenerateCrashReport(OtherPid())`. If you need the crash report ID it will be copied in the second optional parameter upon successful crash report generation. 2562
CrashReporterHost.cpp 9105
CrashReporterHost.h 5161
CrossProcessMutex.h CrossProcessMutex @param name A name which can reference this lock (currently unused) 3424
CrossProcessMutex_posix.cpp 3417
CrossProcessMutex_unimplemented.cpp 1391
CrossProcessMutex_windows.cpp 2034
CrossProcessSemaphore.h CrossProcessSemaphore @param name A name which can reference this lock (currently unused) 3249
CrossProcessSemaphore_posix.cpp static 4263
CrossProcessSemaphore_unimplemented.cpp static 1947
CrossProcessSemaphore_windows.cpp static 2527
EnvironmentMap.h 2346
FileDescriptor.cpp auto_close 4845
FileDescriptor.h 3939
FileDescriptorSetChild.cpp 1007
FileDescriptorSetChild.h 1447
FileDescriptorSetParent.cpp 1083
FileDescriptorSetParent.h 1526
FileDescriptorShuffle.cpp 3720
FileDescriptorShuffle.h 2353
FileDescriptorUtils.cpp 2706
FileDescriptorUtils.h 1643
ForkServer.cpp Prepare an environment for running a fork server. 9151
ForkServer.h 1133
ForkServiceChild.cpp 5225
ForkServiceChild.h This is the interface to the fork server. When the chrome process calls |ForkServiceChild| to create a new process, this class send a message to the fork server through a pipe and get the PID of the new process from the reply. 2806
GeckoChildProcessHost.cpp 61281
GeckoChildProcessHost.h 10210
IOThreadChild.h 1380
IPCMessageUtils.cpp 707
IPCMessageUtils.h Generic enum serializer. Consider using the specializations below, such as ContiguousEnumSerializer. This is a generic serializer for any enum type used in IPDL. Programmers can define ParamTraits<E> for enum type E by deriving EnumSerializer<E, MyEnumValidator> where MyEnumValidator is a struct that has to define a static IsLegalValue function returning whether a given value is a legal value of the enum type at hand. \sa 42484
IPCStream.ipdlh 675
IPCStreamAlloc.h 718
IPCStreamChild.cpp static 4090
IPCStreamDestination.cpp 11255
IPCStreamDestination.h 2518
IPCStreamParent.cpp static 4236
IPCStreamSource.cpp 7883
IPCStreamSource.h 4068
IPCStreamUtils.cpp 17596
IPCStreamUtils.h do something with the nsIInputStream 7552
IPDLParamTraits.h 15581
IdleSchedulerChild.cpp 3084
IdleSchedulerChild.h 1497
IdleSchedulerParent.cpp 9688
IdleSchedulerParent.h 3387
InputStreamParams.ipdlh 2383
InputStreamUtils.cpp 14619
InputStreamUtils.h 4199
LibrarySandboxPreload.cpp 2546
LibrarySandboxPreload.h 599
MessageChannel.cpp IPC design: There are three kinds of messages: async, sync, and intr. Sync and intr messages are blocking. Terminology: To dispatch a message Foo is to run the RecvFoo code for it. This is also called "handling" the message. Sync and async messages can sometimes "nest" inside other sync messages (i.e., while waiting for the sync reply, we can dispatch the inner message). Intr messages cannot nest. The three possible nesting levels are NOT_NESTED, NESTED_INSIDE_SYNC, and NESTED_INSIDE_CPOW. The intended uses are: NOT_NESTED - most messages. NESTED_INSIDE_SYNC - CPOW-related messages, which are always sync and can go in either direction. NESTED_INSIDE_CPOW - messages where we don't want to dispatch incoming CPOWs while waiting for the response. These nesting levels are ordered: NOT_NESTED, NESTED_INSIDE_SYNC, NESTED_INSIDE_CPOW. Async messages cannot be NESTED_INSIDE_SYNC but they can be NESTED_INSIDE_CPOW. To avoid jank, the parent process is not allowed to send NOT_NESTED sync messages. When a process is waiting for a response to a sync message M0, it will dispatch an incoming message M if: 1. M has a higher nesting level than M0, or 2. if M has the same nesting level as M0 and we're in the child, or 3. if M has the same nesting level as M0 and it was sent by the other side while dispatching M0. The idea is that messages with higher nesting should take precendence. The purpose of rule 2 is to handle a race where both processes send to each other simultaneously. In this case, we resolve the race in favor of the parent (so the child dispatches first). Messages satisfy the following properties: A. When waiting for a response to a sync message, we won't dispatch any messages of nesting level. B. Messages of the same nesting level will be dispatched roughly in the order they were sent. The exception is when the parent and child send sync messages to each other simulataneously. In this case, the parent's message is dispatched first. While it is dispatched, the child may send further nested messages, and these messages may be dispatched before the child's original message. We can consider ordering to be preserved here because we pretend that the child's original message wasn't sent until after the parent's message is finished being dispatched. When waiting for a sync message reply, we dispatch an async message only if it is NESTED_INSIDE_CPOW. Normally NESTED_INSIDE_CPOW async messages are sent only from the child. However, the parent can send NESTED_INSIDE_CPOW async messages when it is creating a bridged protocol. Intr messages are blocking and can nest, but they don't participate in the nesting levels. While waiting for an intr response, all incoming messages are dispatched until a response is received. When two intr messages race with each other, a similar scheme is used to ensure that one side wins. The winning side is chosen based on the message type. Intr messages differ from sync messages in that, while sending an intr message, we may dispatch an async message. This causes some additional complexity. One issue is that replies can be received out of order. It's also more difficult to determine whether one message is nested inside another. Consequently, intr handling uses mOutOfTurnReplies and mRemoteStackDepthGuess, which are not needed for sync messages. 94577
MessageChannel.h This sends a special message that is processed on the IO thread, so that other actors can know that the process will soon shutdown. 29668
MessageLink.cpp 12009
MessageLink.h 3817
MessagePump.cpp namespace ipc 12996
MessagePump.h ` The MessagePumpForAndroidUI exists to enable IPDL in the Android UI thread. The Android UI thread event loop is controlled by Android. This prevents running an existing MessagePump implementation in the Android UI thread. In order to enable IPDL on the Android UI thread it is necessary to have a non-looping MessagePump. This class enables forwarding of nsIRunnables from MessageLoop::PostTask_Helper to the registered nsIEventTarget with out the need to control the event loop. The only member function that should be invoked is GetXPCOMThread. All other member functions will invoke MOZ_CRASH 4980
MiniTransceiver.cpp Initialize the IO vector for sending data and the control buffer for sending FDs. 7317
MiniTransceiver.h This simple implementation handles the transmissions of IPC messages. It works according to a strict request-response paradigm, no concurrent messaging is allowed. Sending a message from A to B must be followed by another one from B to A. Because of this we don't need to handle data crossing the boundaries of a message. Transmission is done via blocking I/O to avoid the complexity of asynchronous I/O. 3628
Neutering.h This header declares RAII wrappers for Window neutering. See WindowsMessageLoop.cpp for more details. 1849
PBackground.ipdl Issue an asynchronous request that will be used in a synchronous fashion through complex machinations described in `PBackgroundLSRequest.ipdl` and `LSObject.h`. 8733
PBackgroundSharedTypes.ipdlh 1807
PBackgroundTest.ipdl 496
PChildToParentStream.ipdl 1715
PFileDescriptorSet.ipdl 539
PIdleScheduler.ipdl PIdleScheduler is the protocol for cross-process idle scheduling. Only child processes participate in the scheduling and parent process can run its idle tasks whenever it needs to. The scheduler keeps track of the following things. - Activity of the main thread of each child process. A process is active when it is running tasks. Because of performance cross-process counters in shared memory are used for the activity tracking. There is one counter counting the activity state of all the processes and one counter for each process. This way if a child process crashes, the global counter can be updated by decrementing the per process counter from it. - Child processes running prioritized operation. Top level page loads is an example of a prioritized operation. When such is ongoing, idle tasks are less likely to run. - Idle requests. When a child process locally has idle tasks to run, it requests idle time from the scheduler. Initially requests go to a wait list and the scheduler runs and if there are free logical cores for the child processes, idle time is given to the child process, and the process goes to the idle list. Once idle time has been consumed or there are no tasks to process, child process informs the scheduler and the process is moved back to the default queue. 2664
PParentToChildStream.ipdl 1715
ProcessChild.cpp static 1363
ProcessChild.h Exit *now*. Do not shut down XPCOM, do not pass Go, do not run static destructors, do not collect $200. 1598
ProcessUtils.h 2410
ProcessUtils_bsd.cpp 703
ProcessUtils_common.cpp 6880
ProcessUtils_linux.cpp 590 489
ProcessUtils_none.cpp 500
ProtocolTypes.ipdlh 486
ProtocolUtils.cpp 28362
ProtocolUtils.h 35051
ScopedXREEmbed.cpp 2434
ScopedXREEmbed.h namespace ipc 820
SharedMemory.cpp static 2331
SharedMemory.h 4583
SharedMemoryBasic.h 669
SharedMemoryBasic_android.cpp unused 3304
SharedMemoryBasic_android.h 2007
SharedMemoryBasic_chromium.h 2560
SharedMemoryBasic_mach.h 2970 nothing 24629
SharedMemory_posix.cpp 1098
SharedMemory_windows.cpp 1151
Shmem.cpp 14774
Shmem.h |Shmem| is one agent in the IPDL shared memory scheme. The way it works is essentially (1) C++ code calls, say, |parentActor->AllocShmem(size)| (2) IPDL-generated code creates a |mozilla::ipc::SharedMemory| wrapping the bare OS shmem primitives. The code then adds the new SharedMemory to the set of shmem segments being managed by IPDL. (3) IPDL-generated code "shares" the new SharedMemory to the child process, and then sends a special asynchronous IPC message to the child notifying it of the creation of the segment. (What this means is OS specific.) (4a) The child receives the special IPC message, and using the |SharedMemory{Basic}::Handle| it was passed, creates a |mozilla::ipc::SharedMemory| in the child process. (4b) After sending the "shmem-created" IPC message, IPDL-generated code in the parent returns a |mozilla::ipc::Shmem| back to the C++ caller of |parentActor->AllocShmem()|. The |Shmem| is a "weak reference" to the underlying |SharedMemory|, which is managed by IPDL-generated code. C++ consumers of |Shmem| can't get at the underlying |SharedMemory|. If parent code wants to give access rights to the Shmem to the child, it does so by sending its |Shmem| to the child, in an IPDL message. The parent's |Shmem| then "dies", i.e. becomes inaccessible. This process could be compared to passing a "shmem-access baton" between parent and child. 7579
StringUtil.cpp 2656
TaintingIPCUtils.h 1269
TaskFactory.h This is based on the ScopedRunnableMethodFactory from ipc/chromium/src/base/task.h Chromium's factories assert if tasks are created and run on different threads, which is something we need to do in PluginModuleParent (hang UI vs. main thread). TaskFactory just provides cancellable tasks that don't assert this. This version also allows both ScopedMethod and regular Tasks to be generated by the same Factory object. 2881
Transport.h 1306
TransportSecurityInfoUtils.cpp 1786
TransportSecurityInfoUtils.h 936
Transport_posix.cpp close after sending 2558
Transport_posix.h 1047
Transport_win.cpp 3637
Transport_win.h 3362
URIParams.ipdlh 1929
URIUtils.cpp 3600
URIUtils.h 1424
WindowsMessageLoop.cpp The Windows-only code below exists to solve a general problem with deadlocks that we experience when sending synchronous IPC messages to processes that contain native windows (i.e. HWNDs). Windows (the OS) sends synchronous messages between parent and child HWNDs in multiple circumstances (e.g. WM_PARENTNOTIFY, WM_NCACTIVATE, etc.), even when those HWNDs are controlled by different threads or different processes. Thus we can very easily end up in a deadlock by a call stack like the following: Process A: - CreateWindow(...) creates a "parent" HWND. - SendCreateChildWidget(HWND) is a sync IPC message that sends the "parent" HWND over to Process B. Process A blocks until a response is received from Process B. Process B: - RecvCreateWidget(HWND) gets the "parent" HWND from Process A. - CreateWindow(..., HWND) creates a "child" HWND with the parent from process A. - Windows (the OS) generates a WM_PARENTNOTIFY message that is sent synchronously to Process A. Process B blocks until a response is received from Process A. Process A, however, is blocked and cannot process the message. Both processes are deadlocked. The example above has a few different workarounds (e.g. setting the WS_EX_NOPARENTNOTIFY style on the child window) but the general problem is persists. Once two HWNDs are parented we must not block their owning threads when manipulating either HWND. Windows requires any application that hosts native HWNDs to always process messages or risk deadlock. Given our architecture the only way to meet Windows' requirement and allow for synchronous IPC messages is to pump a miniature message loop during a sync IPC call. We avoid processing any queued messages during the loop (with one exception, see below), but "nonqueued" messages (see under the section "Nonqueued messages") cannot be avoided. Those messages are trapped in a special window procedure where we can either ignore the message or process it in some fashion. Queued and "non-queued" messages will be processed during Interrupt calls if modal UI related api calls block an Interrupt in-call in the child. To prevent windows from freezing, and to allow concurrent processing of critical events (such as painting), we spin a native event dispatch loop while these in-calls are blocked. 45876
WindowsMessageLoop.h namespace windows 3488
components.conf 807 6399
nsIIPCSerializableInputStream.h 6837