1815957 - Investigate GPU process code as design reference for extension process

Status: RESOLVED FIXED

(GeckoView :: General, task, P2)

Comment 1

[Jonathan Almeida [:jonalmeida]]

Post sprint-planning: Demoting this to P2 since no one is assigned and we didn't commit to working on this in 112. The question mark is for sprint planning to consider if we want to add it to the sprint or not. Removing the ? because we have agreed to continue working on this.

Comment 2

[Zac McKenney [:zmckenney]]

Investigation Results (and reason for closing)

After talking with Nika about processes it was decided that changing the process to an AndroidManifest declared process was not necessary. The GPU process has additional functionality that necessitated a separate process handling but for extensions we can utilize the standard content process and add crash handling (which will benefit Desktop as well). There do not appear to be significant benefits to a new process type except for the naming schema.

Currently on Android the extension process will be called a "tab" process similar to all other content processes in the codebase. As seen in about:processes the extension process type can still be found and this can be used when needed to determine which process is for extensions.