Re: Session manager architecture

Skip to first unread message

Gabe Schine

Dec 15, 2020, 1:34:15 PM12/15/20
to Shai Barack, Geevarghese V K, component-framework-dev,


A great question. We are working to rectify this right now. The decision is a legacy one, and was made because when session_manager was introduced, it was not yet possible for tools like session_control to access services exposed by session_manager without putting a v1 component in its ancestral tree.

This restriction no longer exists.

Let us know if you have any other questions!

On Mon, Dec 14, 2020 at 9:24 PM Shai Barack <> wrote:
I believe it's a temporary arrangement for testing. Adding Gabe who knows more. 

On Mon, Dec 14, 2020, 9:14 PM Geevarghese V K <> wrote:
  Dear team,

session manager is a v2 component. Ideally all V2 components are handled by component manager. But there is a difference in the session framework architecture.

The session manager is ran by"fuchsia.session.ElementManager": [ "fuchsia-pkg://", "fuchsia-pkg://" ]

Also the services in the emulator shows that 
 j: 17585             95.2M   95.1M
    p: 17636         2428.4k   2428k     36k
    j: 18716           92.8M   92.8M                 app
      j: 19342        700.4k    700k
        p: 19351      700.4k    700k     36k         sysmgr.cmx
      j: 19964         91.6M   91.5M                 sys

          j: 25835     1853.1k   1852k
                 p: 25860   1120.4k   1120k     36k         component_manager_sfw.cmx
                     j: 29329    304.4k    304k
                         p: 29633  304.4k    304k     36k
                     j: 30569    428.4k    428k
                         p: 30722  428.4k    428k     36k

Why component_manager_sfw is used and why can't session manager be ran by component manager directly?

All posts must follow the Fuchsia Code of Conduct or may be removed.
To unsubscribe from this group and stop receiving emails from it, send an email to

Gabe Schine
Software Engineer / Manager

Reply all
Reply to author
0 new messages