Ubuntu Snap update spoiled my World Cup Final

Re:Ubuntu Snap update spoiled my World Cup Final by toast0 on Monday December 19, 2022 @11:35AM (#34054073)

At start, you could start a new seed process, map all the libraries and what not, but don't do any browsing work... When it's time to launch an isolated process, fork the seed process and use the child.

This doesn't seem insane to me, but might not be an easy thing to fit in to the large body of code that's already there.

You still have issues if you're starting up during an upgrade, but that's a problem with anything dynamically linked.

[ Parent | on HN ]

Re:Ubuntu Snap update spoiled my World Cup Final by iggldiggl on Tuesday December 20, 2022 @04:53AM (#34063800)

Doesn't using fork make it more difficult to cleanly separate the various child processes from each other? It also makes address space layout randomisation less effective, because every forked process starts out with the same base memory layout, doesn't it?

[ Parent | on HN ]

Re:Ubuntu Snap update spoiled my World Cup Final by toast0 on Wednesday December 21, 2022 @09:05PM (#34088839)

> Doesn't using fork make it more difficult to cleanly separate the various child processes from each other?

I don't think so? As long as the main process is separate from the seed process, and the seed process is forked before specialization.

> It also makes address space layout randomisation less effective, because every forked process starts out with the same base memory layout, doesn't it?

Yeah, I think you're right. Not sure if you could maybe do some randomization post fork, but you're probably right.

[ Parent | on HN ]