3 ms·
How does an AppImage handle shared library dependencies? Do multiple independent AppImages share the same mmap'ed library or do they each occupy their own in RA
by jasonzemos 7y ago
How does an AppImage handle shared library dependencies? Do multiple independent AppImages share the same mmap'ed library or do they each occupy their own in RAM? If there's no way to dedup the same dependency code between apps then memory usage can grow out of control pretty easily. Package-based distributions concern themselves with this a lot...
- AnIdiotOnTheNet 7y ago> If there's no way to dedup the same dependency code between apps then memory usage can grow out of control pretty easily. You seriously say this in an era when Electron exists? You'd be hard pressed to waste more resources by simply not having deduped libraries. > Package-based distributions concern themselves with this a lot Yes, and they end up causing a lot more headache than they ever save because of it.
- jasonzemos 7y agoI don't disagree with you at all on principle here. What I'm genuinely curious about is if this approach is akin to "compile everything statically?" I'm assuming that, if so, the issue of memory use has obviously been raised and the response is akin to "memory is cheap now" so it's a bygone concern. That may all be true and totally worth it. I just feel compelled to ask having been accustomed to the shared memory mapping model for decades...