Closing context handles

Depending on mm-renderer's configuration, client applications may be allowed to obtain additional handles to existing contexts. This configuration setting determines mm-renderer's behavior when closing context handles.

Handles obtained by opening existing contexts are called secondary context handles, whereas the handle obtained by creating a context is called the primary context handle. In addition, mm-renderer's configuration may allow a context to exist after its primary handle has been closed. This is called an orphan context. When orphan contexts are allowed, secondary handles are also allowed; however, secondary handles may be allowed when orphan contexts aren't. See the descriptions of the -c and -o command-line options for further clarification.

The behavior of mm-renderer in closing context handles depends on your orphan context policy:

• If orphan contexts are allowed, the only way to close the primary context handle without destroying the context is by explicitly calling mmr_context_close().
• If orphan contexts aren't allowed, there's no way to close the primary handle without destroying the context. In this case, calling mmr_context_close() with the primary context handle is equivalent to calling mmr_context_destroy() because mm-renderer will not only close the context handle but also stop playback, detach any inputs and outputs, and destroy the context. Therefore, you must ensure that any secondary context handles, if permitted, are properly closed.
• Regardless of the configuration, if your application terminates unexpectedly or disconnects from mm-renderer without explicitly closing the primary context handle, the context is destroyed.

In all circumstances, it's important to properly close unneeded context handles to ensure memory leaks don't occur.