-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
avoid loading duplicate libraries #42058
Conversation
We will not use the duplicate, so best to try to avoid loading it.
f2ec633
to
1de1dcd
Compare
Why do we need this? The list of libraries that get loaded this way should be quite short, and never share a basename. |
Some people pre-load libraries, and this helps avoid confusion |
I don't think we should change our behavior by trying to detect |
It also seemed to be one of the possible contributing factors to #40246 |
Why do you think this is a contributing factor? I don't see a connection. |
There's some reports of NULL pointers appearing where they are unexpected, which often is a sign of loading a duplicate library, resulting in the the wrong one being used. This PR solves that. |
We will not use the duplicate, so best to try to avoid loading it. (cherry picked from commit c53669f)
We will not use the duplicate, so best to try to avoid loading it. (cherry picked from commit c53669f)
We will not use the duplicate, so best to try to avoid loading it. (cherry picked from commit c53669f)
We will not use the duplicate, so best to try to avoid loading it. (cherry picked from commit c53669f)
We will not use the duplicate, so best to try to avoid loading it.
We will not use the duplicate, so best to try to avoid loading it.
We will not use the duplicate, so best to try to avoid loading it. (cherry picked from commit c53669f)
We will not use the duplicate, so best to try to avoid loading it.