Bugzilla

(In reply to Jonathan Kew (:jfkthame) from comment #16)
> Does every child do this (e.g. as part of its gfxPlatform initialization), or is it done only on-demand (and if so, how common is that)? I'm wondering because of the risk that the request to the parent could block for a considerable length of time if the parent process is busy.

You're right that this is done by every child process as part of gfxPlatform initialization, and whenever a pref update forced a reload of the color profile. In normal circumstances, that's once per child process.

(In reply to Jonathan Kew (:jfkthame) from comment #16)
> Does every child do this (e.g. as part of its gfxPlatform initialization), or is it done only on-demand (and if so, how common is that)? I'm wondering because of the risk that the request to the parent could block for a considerable length of time if the parent process is busy.

You're right that this is done by every child process as part of gfxPlatform initialization, and whenever a pref update forces a reload of the color profile. In normal circumstances, that's once per child process.

(In reply to Jonathan Kew (:jfkthame) from comment #16)
> Does every child do this (e.g. as part of its gfxPlatform initialization), or is it done only on-demand (and if so, how common is that)? I'm wondering because of the risk that the request to the parent could block for a considerable length of time if the parent process is busy.

You're right that this is done by every child process as part of gfxPlatform initialization, and whenever a pref update forces a reload of the color profile. In normal circumstances, that's once per child process. The main motivation for this message existing is the possibility of a pref change forcing a reload.