Shared DLL Library Isolation #3730
Unanswered
ghost
asked this question in
Various ideas and suggestions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Some software comes with common redist libraries, such as vcruntime140.dll and d3dcompiler_47.dll. Some software needs such libraries, but doesn't include them. In cases when software doesn't include common redist libraries, it usually directs user to install needed libraries system-wide as shared libraries. That creates unnecessary resource sharing, where 2+ programs can share the same or multiple DLL library files from System32/SysWOW64 directory, but the same programs don't share such DLL libraries from mentioned system directories if needed DLL library files already exist in respective programs' own directories.
I think it would be a good feature to have Sandboxie copy/paste common redist library files to sandboxes of programs that need them to reduce resource sharing.
There are library files that can only be used from System32/SysWOW64 or whichever other system directories. I think they are the ones that must be registered as shared library files and usually come with the OS, but standalone versions of redist libraries, such as VC++ 2022, do not have to be registered and can be placed into same directory as executable files of whichever software that uses mentioned libraries.
Beta Was this translation helpful? Give feedback.
All reactions