On 2016-08-30 11:44 AM, Benjamin Smedberg wrote: > This is notice of an intent to change how we export symbols from the > Firefox DLLs and binaries. > > Currently our policy is that extensions may not include binary XPCOM > components, and we've implemented some very basic rules that make it > difficult for extensions to load these components. However, there is > 3rd-party software that continues to use binary XPCOM: either by loading > DLLs using ctypes and then using XPCOM, or injecting DLLs into the > Firefox process. > > Binary injection has been the cause of numerous crash issues in Firefox, > which commonly show up as startup crashes when a Firefox update is first > run. I believe that solving these crashes is a critical part of our > Firefox quality story and our ability to release Firefox updates in a > timely manner. > > To that end, I believe that we should make it technically impossible for > external DLLs to use XPCOM.
Can you please clarify why this proposal is around preventing external DLLs from using XPCOM? In my experience, a good number of the DLLs different programs inject into Firefox are injected using the several facilities that Windows provides for this task, and whether or not those DLLs get access to the symbols currently exported from xul.dll, they can still cause a lot of harm. I'm trying to understand how removing the XPCOM functions they can link against dynamically will improve our situation. Thanks, Ehsan _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
