Another issue I can see... When I started the backup, it replicated itself to use ANOTHER X amount of RAM, and then add on the backup processing...
This is really confusing from a programming perspective. I can understand the fork, but to fork like that is just... not good... If I had it running at 200 MB RAM, and tried backing up, and it consumed another 200 MB RAM.... It puts the parent process to sleep even, and just replicates.. I can understand it in regards to the backup, to consume more RAM and then when it's done it destroys itself and frees up that RAM, but when it's only using an extra 1 MB of RAM, and an extra 20 MB shared RAM from the parent process, it isn't really needed. The backup just finished, the Backup VM window is still open, the child process has become the parent. And is now using more RAM that it was before it started, and the Shared RAM is also higher, because the child became the only remaining entity, since it has killed off the old parent. Thus, I think the way it is is back to front. The child should die after notifying the parent of completion, not the other way around. So currently BEFORE the backup, it was using (approximately) 79 Mb, but AFTER the backup, it's using (approximately) 84 Mb. Because the child process became the parent. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/dad38071-3f82-4234-81f4-24ff8069a61d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
