-
-
Notifications
You must be signed in to change notification settings - Fork 457
Fix Shared Assembly Issue #1036
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
Conversation
|
let's keep this for 1.10.0 so it can go through daily usage tests longer. |
|
This one will break Plugins with shared assembly (for example sqlite). So somehow user may encounter weird issue when installing multiple plugin. |
jjw24
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no need underscores for privates :)
Oh ok, in this case let's roll out for 1.9.3 then. |
|
@taooceros could this potentially solve #1048 and #1046 ? |
I don't think so. They are not related to assembly loading. |
## Bug fixes - Addresses the issue where WindowsSettings plugin results appear higher than other results #1020 - Fixed an issue where full screen mode does not disable hotkey when enabled #1037 - Fixed some potential issues when loading plugins that use shared assembly #1036 - Sorted out a race condition issue causing image loading on some results to fail #1040 - Revised ttf/otf support #935 - Resolved the issue where WebSearch plugin would crash if not connected to internet #977 - Fixed incorrect text for "New Tab" and "New Window" buttons under Settings' default browser section #951 - Fixed typos in plugin title and WindowsSettings name inside the context menu #1056
This fixes the issue where multiple plugins using shared assembly like SQLite, the ones loaded later will not be able to access the shared assembly.
Previous I check all the loaded assembly before allowing the pluginassemblyloader to load the assembly. However, this doesn't seem like a good practice, since this will prevent a assembly context to load the same assembly if another assembly context has already loaded it (which are isolated).
I have tested it for the winrt.dll situation as well. The default assembly loader will load the winrt.dll before we trigger a deferred load so all assembly should be good with that. However, I am curious whether we should match with Name instead of FullName.